You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@dolphinscheduler.apache.org by boyi <zh...@163.com> on 2020/09/29 15:06:47 UTC

[DISCUSS] Change storage method and access control

HI:



This Feature is the front of #3820.

Change 1:

File storage is divided by project.

The currently scheduled file management is stored in hdfs.
The storage path rule is: /dolphinscheduler/tenant code/resources

Change the storage path rule to: /dolphinscheduler/project code/resources

The current version has the following problems.

Complicated permissions division, for example, if there are 100 projects, if there are mutual references, the permissions of the referenced resource files will be very complicated.
Export the project from the development environment, there is no way to split the resource file.

The changes are as follows:

The code field is added to the resource file as a unique identifier. The code is unique within the same project.
The resource files are stored according to the project code.
The permissions part can be the most basic version first, and the people in the same project group can be seen. Later, the catalog can be expanded according to the role.

Change 2: Data sources are divided according to projects. [Similar to file management]

The code field is added to the data source to be used as a unique identifier. The code is unique within the same project.
The data source is stored according to the project code.
The permissions part can be the most basic version first, and the people in the same project group can be seen. Later, the catalog can be expanded according to the role.




Let's discuss how to make it more reasonable

Here the change is quite big, send a text to discuss, good continue to push forward

Make scheduling easier to use







该Feature 为 #3820 的前置.
#3820

变更1 :

文件存储按照项目划分.

目前调度的文件管理是存储在hdfs.
存储路径规则为: /dolphinscheduler/租户编码/resources

变更为存储路径规则为: /dolphinscheduler/项目编码/resources

这样存在以下的问题.
1.权限划分复杂, 比如有100个项目,如果存在相互引用的问题.引用的资源文件权限会很复杂.
2.从开发环境导出项目,资源文件没有办法做到拆分.

变动如下:
1.资源文件增加code字段,用作唯一标识. 同一项目内编码唯一.
2.资源文件按照项目编码进行存储.
3.权限部分可以先做到最基础版, 同一项目组内的人员可见. 后期按角色,目录都可以再扩展.

变更2: 数据源按照项目进行划分. [与文件管理类似]
1.数据源增加code字段,用作唯一标识. 同一项目内编码唯一.
2.数据源按照项目编码进行存储.
3.权限部分可以先做到最基础版, 同一项目组内的人员可见. 后期按角色,目录都可以再扩展.




大家有什么好的想法嘛.

这里变动比较大,发文讨论一下,好继续推进.




--------------------------------------
BoYi ZhangE-mail : zhangboyi_mx@163.com