Serialize restricted collections as regular object #7274
Merged
+39
−32
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
We specially serialize collections/maps inot snapshot using interfaces and calling methods like size() but we restrict this for JDK collections that are guarantee to be only in-memory. For all others we are raising an exception. Instead we should just serialize then as regular object with fields.
shatzi
approved these changes
Jul 8, 2024
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 Does This Do
We specially serialize collections/maps into snapshot using interfaces and calling methods like
size()but we restrict this for JDK collections that are guarantee to be only in-memory. For all others we are raising an exception. Instead we should just serialize then as regular object with fields.Motivation
#7254
Additional Notes
Jira ticket: DEBUG-2502