czy006 opened a new issue, #3355: URL: https://github.com/apache/amoro/issues/3355
### Search before asking - [X] I have searched in the [issues](https://github.com/apache/amoro/issues?q=is%3Aissue) and found no similar issues. ### What would you like to be improved? Currently, we use **Java serialization** and **Kyro serialization**. This serialization method may have some issues, including low performance, We use Kyro serialization for **PUT** and **GET** operations on Rocksdb, which is a lookup join feature in **Mixed Format** In the objects we store in the database, we also need to serialize and deserialize. During the upgrade process, we occasionally encounter deserialization errors and issues (as shown in the figure below) Through research, we found that **[Apache Fury](https://fury.apache.org/)** can improve serialization performance and solve deserialization problems. We will provide performance testing reports in the future to compare before and after replacement ### How should we improve? - Abstract resource serialization interface, implementation of native serialization in current Java, implementation of Kyro serialization - Implement Fury serialization and provide configuration options for Fury serialization, while marking other serialization methods as expired - When the Amoro LTS version is completed, we will remove the implementation of Kyro serialization ### Are you willing to submit PR? - [X] Yes I am willing to submit a PR! ### Subtasks _No response_ ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
