fix: reject duplicate projection output names - #24073
Draft
msaule wants to merge 1 commit into
Draft
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 issue does this PR close?
Rationale for this change
ProjectionExeccan currently be constructed with duplicate output aliases. This violates DataFusion's unique-column-name invariant and makes name-based physical-plan rewrites, including filter pushdown, ambiguous and capable of producing incorrect results.What changes are included in this PR?
ProjectionExec::try_newwith a planning error.Are these changes tested?
cargo test -p datafusion-physical-plan --libcargo clippy -p datafusion-physical-plan --all-targets --all-features -- -D warningsAre there any user-facing changes?
Physical-plan API users that construct a
ProjectionExecwith duplicate output aliases now receive a planning error instead of an ambiguous plan. SQL planning already enforces unique names.