We can rename the current `sharding-rule` to `shardingsphere-rule` which can include sharding, master-slave, encrypt, shadow and so on.
------------------ Liang Zhang (John) Apache ShardingSphere & Dubbo KimmKing <[email protected]> 于2020年5月6日周三 上午11:04写道： > The new structure design will decouple master-slave/encrypt with > sharding-rule, each feature can be idependent now. > > > At 2020-05-05 22:45:54, "Juan Pan" <[email protected]> wrote: > >Hi, > > > > > >It seems a significant change, hope everything goes well. > > > > > >Best wishes > >Trista > > > > > > Juan Pan (Trista) > > > >Senior DBA & PPMC of Apache ShardingSphere(Incubating) > >E-mail: [email protected] > > > > > > > > > >On 05/5/2020 20:14，[email protected]<[email protected]> wrote： > >Hi All, > > > >The pluggable kernel is almost finished[1] expected YAML API changes. > > > >We need to decide how the YAML API adjustment now. I prefer use flat API > >setting with YAML. > > > >The original YAML configuration: > > > >``` > >dataSources: > >ds_0: !!xxx > >xxx > >ds_1: !!xxx > >xxx > > > >shardingRule: > >xxx > >masterSlaveRules: > >xxx > >encryptRule: > >xxx > > > >props: > >xxx.xxx: xxx > >``` > > > >After changes: > > > > > >``` > >dataSources: > >ds_0: !!xxx > >xxx > >ds_1: !!xxx > >xxx > > > >shardingRule: > >xxx > > > >masterSlaveRules: > >xxx > > > >encryptRule: > >xxx > > > >props: > >xxx.xxx: xxx > >``` > > > >All rules are in the same level and can constitute by every type, for > >example: masterSlaveRule and encryptRule. > > > >Looking forward to your suggestions, thank you. > > > > > >[1] https://github.com/apache/shardingsphere/issues/3691 > > > >------------------ > > > >Liang Zhang (John) > >Apache ShardingSphere & Dubbo >
