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?
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?
Benchmark