[Doc][Spec] fury java serialization spec #1238
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
theweipeng
approved these changes
Dec 20, 2023
chaokunyang
changed the title
chaokunyang
changed the title
This was referenced Dec 20, 2023
chaokunyang
added a commit
that referenced
this pull request
Feb 28, 2024
<!-- Thank you for your contribution! Please review https://github.com/alipay/fury/blob/main/CONTRIBUTING.rst before opening a pull request. --> ## What do these changes do? This PR refine fury java serialization format spec. The cross-language object graph serialization spec is similar and will be added in a later PR, but it needs more discuss. This PR added some new spec which hasn't been implemented in current java implementation: - chunk-by-chunk predictive map serialization: #925 - layed class meta - new class meta encoding - #1229 - object serialization with schema evolution support by auto meta share. Some parts has been omitted in this spec: - object serialization with schema evolution support by write field in a KV like pattern: this will be replaced by schema evolution mode described in this spec in the future. Currently fury doesn't provide binary compatibility, the spec may be revised in the future. <!-- Please give a short brief about these changes. --> ## Related issue number <!-- Are there any issues opened that will be resolved by merging this change? --> Closes #1239 #1238 ## Check code requirements - [ ] tests added / passed (if needed) - [ ] Ensure all linting tests pass, see [here](https://github.com/alipay/fury/blob/main/CONTRIBUTING.rst) for how to run them --------- Co-authored-by: Twice <twice@apache.org>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What do these changes do?
This PR formalize fury java specification with following changes:
There are still more improvement space in fury java protocol, such improvements will be added in a follow-up PR.
Related issue number
#1239
Check code requirements