add support for optional fields in records#6669
Merged
Conversation
This commit adds support for optional fields in records making fusing of varied JSON data that arises from common sum types much more uniform. The SUP format is updated with a ? following field names to represent optional fields and _ to represent a field value that is not present. While the SuperSQL parser can parse SUP literals with optional fields, record expressions do not yet support optional fields as this support will come in a subequent PR. The vector representation encodes optional field columns by run-length encoding their presence and generates a slot map on demand when serializing to BSUP or when dereferencing a field to in turn generate a vector.Dynamic mixed with Missing error values. This commit is not backward compatible with previous BSUP versions and we will update the BSUP version nunber in a subsequent PR prior to the RINCON release.
nwt
reviewed
Feb 27, 2026
nwt
reviewed
Feb 27, 2026
nwt
reviewed
Feb 27, 2026
nwt
reviewed
Feb 27, 2026
nwt
approved these changes
Feb 27, 2026
This was referenced Feb 27, 2026
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
2 participants
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.
This commit adds support for optional fields in records making fusing of varied JSON data that arises from common sum types much more uniform. The SUP format is updated with a ? following field names to represent optional fields and _ to represent a field value that is not present.
While the SuperSQL parser can parse SUP literals with optional fields, record expressions do not yet support optional fields as this support will come in a subequent PR.
The vector representation encodes optional field columns by run-length encoding their presence and generates a slot map on demand when serializing to BSUP or when dereferencing a field to in turn generate a vector.Dynamic mixed with Missing error values.
This commit is not backward compatible with previous BSUP versions and we will update the BSUP version nunber in a subsequent PR prior to the RINCON release.