Someone gave me a point to consider the compatibility of the system switching from berkeleydb-je to ZooKeeper.
I am going to provide tools and help documents so that users can use tools to read metadata from the system running on berkeleydb-je, and then import it into the new version system based on ZooKeeper. And I am wondering if the storage implementation of berkeleydb-je can be kept in the project so that everyone can choose by themselves. I understand that after the metadata storage based on ZooKeeper is implemented, the storage of berkeleydb-je has become a non-mandatory dependency. After the implementation is completed, I will ask the mentors for suggestions based on the implementation. Thanks! Goson zhang <[email protected]> 于2022年1月17日周一 11:32写道： > Hi all: > > According to Apache's protocol requirements[1], berkeleydb-je is not a > dependent component that meets Apache's open-source requirements. Next, I > plan to replace it, before finding a better metadata storage component, > with ZooKeeper. > > Let's know your consideration, in order to avoid the impact before and > after the change, we have abstracted the operation of metadata in the early > stage, so that the module can seamlessly migrate this part of the code. > > Thanks! > > 1. https://lists.apache.org/thread/nchbf7zyg78lwh04op2k0634csj8p5yv >
