Skip to content
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

Merged
merged 11 commits into from
Jan 7, 2025

Conversation

orisgarno
Copy link
Contributor

@orisgarno orisgarno commented Jan 6, 2025

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?

  • Does this PR introduce any public API change?
  • Does this PR introduce any binary protocol compatibility change?

Benchmark

@orisgarno orisgarno changed the title fix(java):Compatible mode on de/serialize api failed to deserialize fix(java): Compatible mode on de/serialize api failed to deserialize Jan 6, 2025
@orisgarno orisgarno force-pushed the fix-compatible-mode branch from d9dd748 to 1c7a45f Compare January 6, 2025 12:31
@orisgarno orisgarno marked this pull request as ready for review January 6, 2025 16:15
Copy link
Collaborator

@chaokunyang chaokunyang left a 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

Copy link
Collaborator

@chaokunyang chaokunyang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@chaokunyang chaokunyang merged commit d7ddd90 into apache:main Jan 7, 2025
38 checks passed
@orisgarno orisgarno deleted the fix-compatible-mode branch January 7, 2025 13:39
@orisgarno
Copy link
Contributor Author

@chaokunyang Thanks for merging this PR.
Any idea when is the next release cycle?

@chaokunyang
Copy link
Collaborator

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

@orisgarno
Copy link
Contributor Author

orisgarno commented Jan 8, 2025

Will try to look into that first, i'll reach you out if i have anything to clarify. @chaokunyang
#1870 should fix this right? should i continue this #1870?

@chaokunyang
Copy link
Collaborator

chaokunyang commented Jan 8, 2025

#1870 is handling field type inconsistency, here we are handling pojo root type inconsistentcy, they are different issues. I created a new issue for this #1998

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants