[Question] How to force codegen serializer for custom JDK serialization?
- Dominant language
- Java
- Stars
- 4.5k
- Forks
- 443
- Avg merge
- 5h 59m
- Merged PRs (30d)
- 77
Description
### Question
Hi,
Fury shows the following (correct) warning for one of my classes:
> class xy.SimplePrincipalCollection customized jdk serialization, which is inefficient. Please replace it with a org.apache.fury.serializer.Serializer or implements java.io.Externalizable.
I have no control over this class and cannot write an efficient custom serializer because internals cannot be accessed without reflection. How can I force Fury to use the default JIT/Codegen serializer for this class?
Contributor guide
Research direction
Start by tracing Fury's warning for customized JDK serialization and the serializer-selection path for the affected Java class. The issue names no source files or tests, so first identify the configuration or entry point that controls JIT/Codegen selection; done would require a documented or implemented way to force that serializer without access to the class internals.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100