menghaoranss opened a new issue #4778: Optimize configuration structure of config®istry center URL: https://github.com/apache/incubator-shardingsphere/issues/4778 For #4522 Based on the completed split of the config center and registry center, the related configuration structure will be adjusted as follows: #### Current structure ``` / ├─orchestration-namespace ├─orchestration-name │ ├─config │ │ ├─authentication │ │ ├─props │ │ ├─schema │ │ │ ├─sharding-schema-name │ │ │ │ ├─datasource │ │ │ │ └─rule │ │ │ ├─encrypt-schema-name │ │ │ │ ├─datasource │ │ │ │ └─rule │ │ │ └─master_slave-schema-name │ │ │ │ ├─datasource │ │ │ │ └─rule │ ├─state │ │ ├─datasources │ │ └─instances ``` #### New structure ##### config center ``` / ├─orchestration-namespace ├─orchestration-name │ ├─config │ │ ├─authentication │ │ ├─props │ │ ├─schema │ │ │ ├─sharding-schema-name │ │ │ │ ├─datasource │ │ │ │ ├─rule │ │ │ │ └─type │ │ │ ├─encrypt-schema-name │ │ │ │ ├─datasource │ │ │ │ ├─rule │ │ │ │ └─type │ │ │ └─master_slave-schema-name │ │ │ │ ├─datasource │ │ │ │ ├─rule │ │ │ │ └─type ``` ##### registry center ``` / ├─orchestration-namespace ├─orchestration-name │ ├─registry │ │ ├─states │ │ └─instances ``` Note: + Add a new schema type node under schema node of config center to distinguish the current scheme configuration type (sharding / encrypt / master-slave) (previously judged according to rule content, content may be modified or optimized, which is not beneficial expansion), the type node content contains : + SHARDING + ENCRYPT + MASTER_SLAVE + SHADOW + Split the registry and modify state node to registry node to match the registry + Modify the datasources node of registry center to states, currently used to record the status of slave database Task lists: [ ] 1. Persist and get schema type from type node of config center [ ] 2. Refactor persist and get configuration from registry center [ ] 3. Refactor the judgment logic and code reference of the schema type [ ] 4. Refactor unit tests [ ] 5. Refactor UI Any suggestions， please reply directly to this issue.
---------------------------------------------------------------- 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
