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
[SPARK-34576][SQL][3.1] Fix drop/add columns to a dataset of DESCRIBE COLUMN
#31727
Conversation
FYI @cloud-fan |
Kubernetes integration test starting |
Kubernetes integration test status success |
Test build #135714 has finished for PR 31727 at commit
|
retest this please |
Kubernetes integration test starting |
Kubernetes integration test status success |
Test build #135728 has finished for PR 31727 at commit
|
seems like a real test failure. |
@cloud-fan Seems we should backport more pr to 3.1 branch according to the failed test. |
ah we don't have v2 DESC COLUMN in 3.1, so the bug doesn't exist there. Let's close this PR. |
What changes were proposed in this pull request?
In the PR, I propose to generate "stable" output attributes per the logical node of the DESCRIBE COLUMN command.
Why are the changes needed?
This fixes the issue demonstrated by the example:
Does this PR introduce any user-facing change?
After this change user
drop()/add()
works well.How was this patch tested?
Added UT