allow on-the-fly migration of primitive vs. boxed fields #44
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Establishes wire compatibility of boxed and primitive types of the same content, obsoleting the need for declaring a new field and bridging with wrappers. The @externalize annotation has been enhanced to provide fine-grained control, defaulting to established practice.
The pLongNullValue attributes et.al. define the primitive value to be equivalent to null, which is implicitly applied to the field whenever null is read from the input.
The sparseBoxed attribute defines whether this conversion is to be mirrored when converting from primitive to boxed values, i.e. null is applied to the field whenever the corresponding value is encountered.
All null-equivalent values default to zero / false, while sparse boxing is enabled by default.