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): fix find constructor error in generated serializer class caused by duplicated class classloading for Fury #1948

Merged
merged 4 commits into from
Nov 21, 2024

Conversation

chaokunyang
Copy link
Collaborator

@chaokunyang chaokunyang commented Nov 20, 2024

What does this PR do?

fix duplicate classloading in parent classloader.

Some classloader such as flink classloader can load class from children classloader. If fury is located in children classloader, but we are serializing a class in such parent class, the parent class will load Fury class again, which caused two Fury clases loaded.

Related issues

Closes #1947

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

@chaokunyang chaokunyang changed the title fix(java): fix duplicate classloading in flink user classloader fix(java): fix no constructor in generated serializer class caused by duplicated parent classloading for Fury Nov 20, 2024
@chaokunyang chaokunyang changed the title fix(java): fix no constructor in generated serializer class caused by duplicated parent classloading for Fury fix(java): fix find constructor error in generated serializer class caused by duplicated class classloading for Fury Nov 21, 2024
@chaokunyang chaokunyang merged commit a3a2238 into apache:main Nov 21, 2024
39 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants