MiaoSO commented on issue #1279: [BUG] After I delete Project or User URL: https://github.com/apache/incubator-dolphinscheduler/issues/1279#issuecomment-557347253 (1). Delete the Project Premise: Ordinary user, create project, create workflow and save Normal operation: Normal user or administrator user, enter "Project", delete the project operation, prompt "please delete the process definitions in project first! " Extreme operation: Use the administrator account, enter "Security -> User Manage", delete the ordinary user, prompt "Seccess". The following phenomena may occur: 1. Super administrator account, enter project management page, and the project created by the deleted user does not exist. 2. In the Mysql database, in the t_escheduler_project table, the deleted project created by the user exists. 3. Enter the project management page with any account, create the project with the same name as the deleted project, and create it successfully. 4. Super administrator account, enter "Security -> User Manage", when authorizing the project for the user, it will show the project that does not exist in the project management page but exists in the Mysql table (2). Delete the User Premise: delete the user and the following problems will occur: 1.All resources created by the deleted user will still be in the HDFS platform and Mysql table, and all resources of the user cannot be used through the UI. 2.Project created by deleted users will also be removed, the administrator account to check the project management will find the project which created the user does not exist, but in Mysql table the project still exist. If the project had been empowerment to others before delete user action, the deleted items will still be shown in "Security -> User Manage -> Grant authority -> Project " The following is the self-test recovery operation: Step 1: use the administrator account to enter the "Resources" and delete all resources belonging to the deleted user Step 2: delete the resources created by the user on the HDFS platform (if the user has a tenant migration operation, delete the files belonging to the user under the old tenant) Step 3: if the deleted user has created an item, delete the data corresponding to the user in the Mysql table t_escheduler_project (the project record created by the user). Step 4: if the deleted user has created a project, then cancel the assignment of other users belonging to the project created by the user (or delete Mysql table t_escheduler_relation_project_user related data). Step 5: if the deleted user has created a datasource, the datasource will be unavailable, and the prompt "resource not exist" will be prompted. Delete the data corresponding to the user in the Mysql table t_escheduler_datasource (the record of the datasource created by the user). Step 6: If the deleted user has an item that is authorized, and in the item that is authorized, a workflow definition has been created. It will appear that, the workflow definition created by the deleted user will be unavailable. It is necessary to change the Mysql table "t_escheduler_process_definition". The "user_id" of the related workflow is the user ID or administrator user ID that has permissions for the project.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
