You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@dolphinscheduler.apache.org by GitBox <gi...@apache.org> on 2019/11/26 08:34:48 UTC

[GitHub] [incubator-dolphinscheduler] MiaoSO edited a comment on issue #1333: [discussion] how to redesign Permission

MiaoSO edited a comment on issue #1333: [discussion] how to redesign Permission
URL: https://github.com/apache/incubator-dolphinscheduler/issues/1333#issuecomment-558520811
 
 
   After tested version 1.1, the following is my advice.
   
   1. Tenant
   In my opinion, tenants need to be empowered. Some administrator tenants(such as HDFS and Hive) are at risk if they are exposed to ordinary users.
   Suggest  change "Tenant Name" could not non-repeatable
   
   2. Resources
   (1) I personally think that there is no need to involve the tenant. 
   I don't agree with the design that the user tenant will copy the files to the directory of the new tenant, which will cause file redundancy(From the results of testing on HDFS, other file centers have not tested).
   (2) Enter "Resources-> FIle Manage"
   Suggest change "Name and FileName" to "FileName, MD5Name (FileName+owner+createtime to unique identifier), Owner, LastModifyUser".
   The FileName of the same user cannot be duplicated, and the HDFS storage file name is MD5Name. The files are placed in one directory.
   File permissions can be designed to make the files visible to team members in the project or to themselves
   
   3. Project 
   The project created by the administrator, the administrator has the highest authority of the project.
   Ordinary users can only in the project development for workflow
   
   4. Process definitions
   The user of the workflow is recommended to bind to the project ID, not the user. 
   If the user is deleted, the workflow invalidation is an unreasonable design.
   

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services