[WIP][DRAFT][SQL] Allow DROP TABLE to drop VIEW #53342
Draft
+41
−12
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pan3793
reviewed
Dec 5, 2025
sql/catalyst/src/main/scala/org/apache/spark/sql/internal/SQLConf.scala
Outdated
Show resolved
Hide resolved
Member
|
does it work on temp view and global temp view too? |
uros-db
force-pushed
the
drop-table-view
branch
from
e3be28b to
2b42acc
Compare
uros-db
changed the title
Contributor
Author
Marked the PR as Draft for now, will get back to this a bit later. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Note: experimental / draft PR.
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 TABLEcommand to operate on views, to improve usability and convenience for users. Currently in Spark, attemptingDROP TABLE <view>results in aWRONG_COMMAND_FOR_OBJECT_TYPEerror even though the intent is unambiguous and the operation is safe. Allowing DROP TABLE to drop views 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 theVIEW, instead of returning aWRONG_COMMAND_FOR_OBJECT_TYPEerror.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.