fix: Improve error message for metadata conflict in schema - #23952
Draft
mkleen wants to merge 2 commits into
Draft
fix: Improve error message for metadata conflict in schema#23952mkleen wants to merge 2 commits into
mkleen wants to merge 2 commits into
Conversation
mkleen
force-pushed
the
improve-err-schema-mismatch
branch
3 times, most recently
from
July 29, 2026 10:20
b541f02 to
0cf026b
Compare
mkleen
force-pushed
the
improve-err-schema-mismatch
branch
from
July 29, 2026 10:49
0cf026b to
745aed7
Compare
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.
Which issue does this PR close?
join_selectionflips schema-level metadata, failing "Schema mismatch" #23461Rationale for this change
Based on the discussion in #23461 this pr improves the error message when there is a metadata conflict when schemas get merged. It also reverts #23605, so
CrossJoinExechas again it's original behavior.What changes are included in this PR?
CrossJoinExecphysical_planner.rstest_context.rsmetadata.sltAre these changes tested?
Yes
Are there any user-facing changes?
Yes, error message improved when the schema metadata has conflicting keys using a cross-join.