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.

Sign up for GitHub

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

Jump to bottom

Version tolerance rquirements #33

Closed
rogeralsing opened this issue Jul 18, 2016 · 3 comments
Closed

Version tolerance rquirements #33

rogeralsing opened this issue Jul 18, 2016 · 3 comments
Labels
enhancement help wanted

Comments

@rogeralsing
Copy link
Collaborator

The current plan for version tolerance is to support added and removed fields.
If there is a type missing, there is nothing to generate the reader from, and thus we cannot support this today.

User feedback is welcome
@veblush
Copy link
Contributor

veblush commented Jul 19, 2016 •
edited
Loading

How about writing type manifests into versionTolerantHeader to support type changes. It could be quite often to change integer types such as int to long, etc.

@rogeralsing
Copy link
Collaborator Author

@veblush that is a great idea.
I would like to make this configurable to allow users to opt in/out of less/more tolerance.
Also related to #66

@rogeralsing
Copy link
Collaborator Author

I would like to add an identifier to the ValueSerializerFactories too, so that this ID is emitted together with the typename/id. allowing version tolerant readers to read streams where even types have been removed

@rogeralsing rogeralsing mentioned this issue Dec 9, 2016
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement help wanted
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rogeralsing @veblush