menghaoranss commented on issue #7325:
URL: https://github.com/apache/shardingsphere/issues/7325#issuecomment-689275286
@dongzl , there is the old data structure:
```
├─orchestration-name
│ ├──config
│ │ ├──authentication
│ │ ├──props
│ │ ├──schema [${schema_1},${schema_2}]
│ │ │ ├──${schema_1}
│ │ │ │ ├──datasource
│ │ │ │ ├──rule
│ │ │ ├──${schema_2}
│ │ │ │ ├──datasource
│ │ │ │ ├──rule
│ │ ├──....
│ ├──registry
│ │ ├──datasources
│ │ │ ├──${schema_1}
│ │ │ │ ├──${datasource_1}[DISABLED]
│ │ │ │ ├──${datasource_2}[DISABLED]
│ │ │ ├──${schema_2}
│ │ │ ├──....
│ │ ├──instances
│ │ │ ├──${IP1@PID1@UUID}
│ │ │ ├──${IP2@PID2@UUID}
│ │ │ ├──....
│ │ ├──metadata
│ │ │ ├──${schema_1}
│ │ │ ├──${schema_2}
│ │ │ ├──....
```
1. Remove `config` and `registry` , because they could not describe the
specific role of nodes accurately.
2. Define `schemas` node and move `metadata` to `/schemas/schema_name/table`
.
3. `state` node persist all runtime status, `datanodes` persist real db
nodes status, `proxynodes` persist proxy and jdbc nodes status (jdbc is
understood as an embedded proxy)
----------------------------------------------------------------
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]
