doc: No longer suggest Kryo serialization #31448
Merged
Conversation
This file contains hidden or 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
The use of Kryo to serialize data which is expected to be deserialized by a process not running at the time of the serialization is not recommended.
johanandren
approved these changes
Jun 28, 2022
|
thanks |
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.
These recommendations are likely vestiges of a pre-Jackson past.
Kryo as a serialization format is likely still OK for remoting serialization, but its maintainers have stated that they do not want to have backward/forward-compatibility hold back development, which makes its use for persistence problematic as any version upgrade may render persisted states/events unreadable. A Chill maintainer has commented that one "should never store kryo data beyond the life of a single process".
If you have used Kryo as a persistence serialization, it is recommended to explore other serialization options.