-
Notifications
You must be signed in to change notification settings - Fork 28.9k
[SPARK-12841][SQL][branch-1.6] fix cast in filter #10819
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
cc @yhuai |
|
Can you update the pull request description to include more information? The old pull request description is good. |
|
Test build #49633 has finished for PR 10819 at commit
|
|
retest this please |
|
Test build #49635 has finished for PR 10819 at commit
|
|
test this please |
|
Test build #49638 has finished for PR 10819 at commit
|
|
something wrong with branch 1.6? cc @JoshRosen |
|
There might be something wrong with that build workspace's Ivy cache. If you have Jenkins access, you should be able to SSH in and wipe it away. |
|
retest this please |
|
Test build #49655 has finished for PR 10819 at commit
|
|
Thanks! Merging to branch 1.6. |
In SPARK-10743 we wrap cast with `UnresolvedAlias` to give `Cast` a better alias if possible. However, for cases like filter, the `UnresolvedAlias` can't be resolved and actually we don't need a better alias for this case. This PR move the cast wrapping logic to `Column.named` so that we will only do it when we need a alias name. backport #10781 to 1.6 Author: Wenchen Fan <[email protected]> Closes #10819 from cloud-fan/bug.
|
@cloud-fan you'd need to close this pull request yourself since it was not merged into master. |
In SPARK-10743 we wrap cast with
UnresolvedAliasto giveCasta better alias if possible. However, for cases like filter, theUnresolvedAliascan't be resolved and actually we don't need a better alias for this case. This PR move the cast wrapping logic toColumn.namedso that we will only do it when we need a alias name.backport #10781 to 1.6