THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
State
[Progress record]: Tao Zhiqiang has claimed
Proposed time: 2022/05/11
Discussion time:
Acceptance time:
Complete time:
[issues]：
[email]： casionone@gmail.com
[release]:
[proposer]：casionone
Motivation & Background
At present, linkis's own services involve a lot of basic data, including but not limited to configuration data, dictionary data, etc. Currently, there is no better unified entry for viewing and management.
Data source authority management, usually, only administrators have the authority to maintain data source information, because database passwords and the like are sensitive information. The administrator should manage the data source information in a unified manner. Users of different business types, on the platform, apply for data source access or usage rights under the corresponding business domain. Only after the user and the data source are successfully bound, the user has the right to access the data source. detailed connection information, and then switch to use it in the Scripts JDBC engine, or use it in other application systems.
Basic concept
Expect to achieve goals
- Management of error code configuration
- UDF class configuration
- Data source type configuration and permission management
- Data source cluster environment configuration
- Gateway Token configuration
- Yarn cluster resource address configuration
- UDF administrator configuration
- Data source permission configuration
Implementation plan
- Visualized addition, deletion, modification, and query of operation and maintenance of database tables
- Data source authority control, the data source information is maintained by the administrator. Ordinary users should apply for the data source to be viewed first. The administrator approves the user's application. After the user and the data source information are bound, ordinary users can view the data source. detailed configuration information, and use it in other application systems
Things to Consider & Note:
- Permission problem, only administrators can modify, all users can view?
- After some data is modified, the refresh aging problem
Changes
| Modification | Detail | |
|---|---|---|
| 1 | Modification of maven module | |
| 2 | Modification of HTTP interface | |
| 3 | Modification of the client interface | |
| 4 | Modification of database table structure | |
| 5 | Modification of configuration item | |
| 6 | Modification Error code | |
| 7 | Modifications for Third Party Dependencies |
Compatibility, Deprecation, and Migration Plan
- What impact (if any) will there be on existing users?
- If we are changing behavior, how will we phase out the older behavior?
- If we require special migration tools, describe them here.
- When will we remove the existing behavior?