SerializerPojo: rename already serialized classes
Open
Nobody has claimed this yet.
4.0
enhancement
serialization
- Dominant language
- Java
- Stars
- 5.1k
- Forks
- 877
- PR merge metrics
- No merged PRs in 30d
Description
- If I rename a serializer, mapDB will throw a ClassNotFoundException.
Consider allowing one to change serializer/refactor after the fact
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing SerializerPojo and the ClassNotFoundException path when a serialized class or serializer is renamed. Determine how serialized class names are stored and what compatibility behavior is required; done means existing data remains readable after the rename, with coverage for that scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100