[SPARK-50690][SQL] Fix discrepancy in DESCRIBE TABLE view query output columns quoting #49321
Conversation
This file contains 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
cloud-fan
approved these changes
Dec 27, 2024
HyukjinKwon
approved these changes
Dec 28, 2024
|
Merged to master. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What changes were proposed in this pull request?
Previously, the
DESCRIBE TABLESQL command displayed column lists such as bucket and sort columns as so:However view query output columns were not quoted:
This PR fixes the discrepancy by quoting the view query output columns with ``:
Why are the changes needed?
The change ensures cohesive
DESCRIBE TABLEoutput, which can improve parsing and readability.Does this PR introduce any user-facing change?
Yes, this modifies the view query output columns portion of the
DESCRIBE TABLEoutput.How was this patch tested?
Existing SQL tests, including golden file output
Was this patch authored or co-authored using generative AI tooling?
No