-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-37332][SQL] Allow ANSI intervals in ALTER TABLE .. ADD COLUMNS
#34600
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
v1 Hive external catalog supports |
Thanks. I have corrected the description. |
|
@cloud-fan @sarutak @Peng-Lei @AngersZhuuuu Could you review this PR, please. |
|
@cloud-fan FYI, Here is the ticket for fully unified tests of |
|
Kubernetes integration test starting |
I think Hive external catalog supports ANSI intervals. In this case, the format of metadata is not Hive compatible but Spark specific. |
|
Kubernetes integration test status failure |
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
|
Test build #145230 has finished for PR 34600 at commit
|
...re/src/test/scala/org/apache/spark/sql/execution/command/AlterTableAddColumnsSuiteBase.scala
Show resolved
Hide resolved
|
Test build #145233 has finished for PR 34600 at commit
|
@cloud-fan I have added one. |
ALTER TABLE .. ADD COLUMNSALTER TABLE .. ADD COLUMNS
sarutak
left a comment
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.
LGTM. Pending CIs.
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
|
Test build #145241 has finished for PR 34600 at commit
|
|
I cloned So, I think the |
|
Merging to master. Thank you, @sarutak and @cloud-fan for review. |
What changes were proposed in this pull request?
In the PR, I propose to allow ANSI intervals: year-month and day-time intervals in the
ALTER TABLE .. ADD COLUMNScommand for tables in v1 and v2 In-Memory catalogs. Also added an unified test suite to migrate related tests in the future.Why are the changes needed?
To improve user experience with Spark SQL. After the changes, users will be able to add columns with ANSI intervals instead of dropping and creating new table.
Does this PR introduce any user-facing change?
In some sense, yes. After the changes, the command doesn't output any error message.
How was this patch tested?
By running new test suite: