Hi, all I have created a issue[1] for discussing about optimizing metadata model.
Currently ShardingSphere metadata was only used by sharding & encrypt scenario, master-slave case have to get them from underlying ResultSet meta in sharding-proxy. It is better to establish an global MetaData mechanism which provide uniform interface for initialization, read, refreshing instead of distinguish with usage scenario I think it would be a big refactor for sharding-jdbc & sharding-proxy. assume that task list is as below 1. investigate the usage of current metadata, clarify the function list of metadata (SQLParse, Route,Rewrite etc) 2. design a MetaData Model & MetaData service, at first only consider about storing in memory 3. then consider about migrating to zookeeper or other registration [1]: https://github.com/apache/incubator-shardingsphere/issues/3922 <https://github.com/apache/incubator-shardingsphere/issues/3922> Any thought? ------------------ Zhao Jun (cherrylzhao) Apache ShardingSphere & ServiceComb
