-
Notifications
You must be signed in to change notification settings - Fork 263
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(java): Compatible mode on de/serialize api failed to deserialize #1996
Conversation
d9dd748
to
1c7a45f
Compare
java/fury-format/src/test/java/org/apache/fury/format/type/DataTypeTest.java
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM overall, just a few minor comments
Co-authored-by: Shawn Yang <[email protected]>
Co-authored-by: Shawn Yang <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@chaokunyang Thanks for merging this PR. |
AS the #1972 (comment) said, current way to deserialize the data into another type nees class registration, this is not flexible, we'd better support automatic deserializing into another type before making a release. Would you like to help? @orisgarno |
Will try to look into that first, i'll reach you out if i have anything to clarify. @chaokunyang |
What does this PR do?
Read and write class data on COMPATIBLE mode for de/serializeJavaObject api.
When COMPATIBLE mode is on and need to serialize and deserialize different POJO, users are required to register classes those are going to be serialized or deserialized.
Related issues
Does this PR introduce any user-facing change?
Benchmark