HIVE-29604: DESCRIBE column runs into execution error for partition c…#6472
Merged
Conversation
asf-ci-hive
added
tests pending
tests unstable
tests failed
tests passed
and removed
tests pending
tests unstable
tests failed
labels
deniskuzZ
reviewed
May 13, 2026
deniskuzZ
reviewed
May 13, 2026
deniskuzZ
reviewed
May 13, 2026
asf-ci-hive
added
tests pending
tests unstable
tests passed
and removed
tests passed
tests pending
tests unstable
labels
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
…olumns
What changes were proposed in this pull request?
Fix DESCRIBE query for partition column running into Execution error
Why are the changes needed?
To fix Execution error for DESCRIBE partition column query
Does this PR introduce any user-facing change?
Yes. DESCRIBE query for partition column runs into Execution error currently, this patch fixes it to produce the required output.
How was this patch tested?
Manual Testing + Added failing case in Qtest