It looks good but how about shardingsphere-plugin release cycle? is it the same with shardingsphere? and who will be responsible for the maintenance and compatibility?
Regards, Zheng Feng Zhengqiang Duan <duanzhengqi...@apache.org> 于2023年6月26日周一 19:46写道： > Hi community, > > Due to the rapid development of ShardingSphere, plugin submodules are > currently extracted from both sharding and encrypt modules to store some > special algorithms contributed by the community, such as cosId, nanoid > sharding > algorithm, and sm3 and sm4 encryption algorithms. These plugins enrich the > applicable scenarios of ShardingSphere, but also make ShardingSphere > bloated and complicated. > > . > ├── encrypt > │ ├── api > │ ├── core > │ ├── distsql > │ └── plugin > └── sharding > ├── api > ├── core > ├── distsql > └── plugin > > In order to reduce the dependence on some special jar packages, such as: > cosid, bcprov-jdk15on, we can move the code in the plugin to an independent > shardingsphere-plugin repository, and community contributors can contribute > more algorithm implementations in this repository. > > When users want to use the algorithm in shardingsphere-plugin repository, > they only need to package the algorithm and add the jar to ShardingSphere. > > Considering that this task will take some time to apply for a new > repository, I suggest implementing it in two stages as follows: > > - first, remove plugin document in ShardingSphere > - second, move plugin code and document to shardingsphere-plugin > repository > > Everyone is welcome to participate in the discussion and express their > views. Thank you. > > For more details, you can also refer github issue - > https://github.com/apache/shardingsphere/issues/26590. > > Best regards, > Zhengqiang > —————————————————————— > Zhengqiang Duan (duanzhengqi...@apache.org) > Apache ShardingSphere PMC > GitHub@strongduanmu >
