fix: calling with_column twice and using a window function for the 2nd call returns an error
#12428
Conversation
This file contains 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
My mental model for `with_column` is sugar for `df.select([wildcard(), expr.alias(name)])`. The bug test-case passes with this implementation, but a few other test cases fail. Those test cases resolve around ambiguity in column names, which I *think* I can solve by using `WildcardOptions`.
Michael-J-Ward
changed the title
with_column twice and using a window function for the 2nd call returns an error
|
Alternative approach: #12431 |
The sugared version uses a wildcard to express the previous columns
The ambiguous projection now does not occur until the `physical` stage. I assume there's a way to expand the wildcard and catch it during the `logical` stage, but I haven't found it yet.
…ing wildcardoptions There's still a TODO because I'm not sure **how** to construct the WildcardOptions, but this captures the semantic behavior.
|
is this PR similar to #12431 ? |
|
@comphead yes. I started this draft late last night but hit a block, then Tim put up his working implementation this morning. Purely for the benefit of my own understanding, could you take a look at my proposed impl and let me know if that captures the intended semantic behavior of the function? I'm still building my understanding of the |
This pull request was closed.
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.
DRAFT
My first attempt was to convert
with_columnto a sugar API fordf.select(vec![wildcard(), expr.alias(name)]), which mostly matches my mental model of what the function should do.There are currently failing test cases surrounding ambiguous and/or "over-write an existing column" use cases. I suspect proper use of
WildcardOptionswill let me resolve those.Which issue does this PR close?
Closes #12425.
Rationale for this change
What changes are included in this PR?
Are these changes tested?
Are there any user-facing changes?