-
Notifications
You must be signed in to change notification settings - Fork 28.1k
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-36895][SQL][FOLLOWUP] CREATE INDEX command should rely on the analyzer framework to resolve columns #34467
Conversation
Kubernetes integration test starting |
Kubernetes integration test status failure |
Test build #144845 has finished for PR 34467 at commit
|
@@ -4439,7 +4439,7 @@ class AstBuilder extends SqlBaseBaseVisitor[AnyRef] with SQLConfHelper with Logg | |||
indexName, | |||
indexType, | |||
ctx.EXISTS != null, | |||
columns.map(FieldReference(_).asInstanceOf[FieldReference]).zip(columnsProperties), | |||
columns.map(UnresolvedFieldName(_)).zip(columnsProperties), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just noticed this failed with scala 2.13. Add .toSeq
?
Kubernetes integration test starting |
Kubernetes integration test status failure |
Test build #144851 has finished for PR 34467 at commit
|
The GA failure doesn't seem to be relevant to this PR. I will merge. |
Merged to master. Thank you very much! @cloud-fan |
What changes were proposed in this pull request?
This PR leverages the existing framework to resolve columns in the CREATE INDEX command.
Why are the changes needed?
To fail earlier instead of passing invalid column names to v2 sources.
Does this PR introduce any user-facing change?
no
How was this patch tested?
new test