[PROTOCOL RFC] Full Void Type Support#7073
Open
ZiyaZa wants to merge 1 commit into
Open
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
1 participant
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.
Which Delta project/connector is this regarding?
Description
Associated Github issue for discussions: #7072
This PR adds the proposed protocol change for full VOID support everywhere in Delta table schema. Current protocol is being clarified in #6966 to specify how VOID currently needs to be handled, but this RFC further defines a new table feature that will allow tables to persist VOID columns as UNKNOWN type in Parquet, and hence lift the schema limitations we have today.
How was this patch tested?
N/A
Does this PR introduce any user-facing changes?
Creates a new Protocol RFC.