Union schema can't be a subset of the child schema#8408
Merged
alamb merged 2 commits intoapache:mainfrom Dec 5, 2023
Merged
Conversation
github-actions
Bot
added
core
7 tasks
alamb
approved these changes
Dec 5, 2023
Contributor
alamb
left a comment
alamb
left a comment
There was a problem hiding this comment.
The fact all the tests pass looks good to me. Thank you @jackwener -- nice cleanup
appletreeisyellow
pushed a commit
to appletreeisyellow/datafusion
that referenced
this pull request
Dec 15, 2023
Co-authored-by: Andrew Lamb <andrew@nerdnetworks.org>
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.
Which issue does this PR close?
Closes #.
Rationale for this change
Union
schemacan't be a subset of the child schema, so we can remove useless codeWhat changes are included in this PR?
Are these changes tested?
Add
sltto cover more conditionAre there any user-facing changes?