uros-db opened a new pull request, #53342:
URL: https://github.com/apache/spark/pull/53342
<!--
Thanks for sending a pull request! Here are some tips for you:
1. If this is your first time, please read our contributor guidelines:
https://spark.apache.org/contributing.html
2. Ensure you have added or run the appropriate tests for your PR:
https://spark.apache.org/developer-tools.html
3. If the PR is unfinished, add '[WIP]' in your PR title, e.g.,
'[WIP][SPARK-XXXX] Your PR title ...'.
4. Be sure to keep the PR description updated to reflect all changes.
5. Please write your PR title to summarize what this PR proposes.
6. If possible, provide a concise example to reproduce the issue for a
faster review.
7. If you want to add a new configuration, please read the guideline first
for naming configurations in
'core/src/main/scala/org/apache/spark/internal/config/ConfigEntry.scala'.
8. If you want to add or modify an error type or message, please read the
guideline first in
'common/utils/src/main/resources/error/README.md'.
-->
### What changes were proposed in this pull request?
Modify DROP TABLE command semantics:
`DROP TABLE <view>` **should** work on views.
### Why are the changes needed?
Allow the `DROP TABLE` command to operate on views, to improve usability and
convenience for users. Currently in Spark, attempting `DROP TABLE <view>`
results in a `WRONG_COMMAND_FOR_OBJECT_TYPE` error even though the intent is
unambiguous and the operation is safe. Also, allowing DROP TABLE to drop views
improves aligns Spark with broader SQL ecosystem expectations, and reduces
friction when migrating workloads from other systems. This change simplifies
user code paths by removing the need to special-case view handling in DROP
statements.
### Does this PR introduce _any_ user-facing change?
Yes, the `DROP TABLE <view>` will now drop the `VIEW`, instead of returning
a `WRONG_COMMAND_FOR_OBJECT_TYPE` error.
### How was this patch tested?
Added appropriate SQL tests to verify the new behaviour.
Also, updated the existing tests to match the proposed spec.
### Was this patch authored or co-authored using generative AI tooling?
No.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
