EsotericSoftware/kryo

VersionedRecordSerializer?

Open

#884 opened on Feb 14, 2022

View on GitHub
 (11 comments) (0 reactions) (0 assignees)HTML (6,052 stars) (816 forks)batch import
feature requesthelp wanted

Description

Is your feature request related to a problem? Please describe. I'm trying to serialize a Record that evolves - new components are being added to it.

Describe the solution you'd like Would it make sense to create a VersionedRecordSerializer akin to VersionedFieldSerializer with the same functionality, the @Since annotation?

Describe alternatives you've considered An obvious workaround is to use a traditional class instead of a record.

Contributor guide

Tech stack
java
Domain
backend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
JavaKryo basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Examine the existing VersionedFieldSerializer implementation and the @Since annotation. The issue proposes a similar serializer for Records. The workaround using a traditional class suggests the current Record serialization lacks versioning. A solution would involve extending Kryo's RecordSerializer to support @Since, similar to FieldSerializer. The discussion may indicate design choices. Review comments for maintainer feedback.