HIVE-28591: Fix partition column names evaluation in Vectorizer#validateInputFormatAndSchemaEvolution #5519
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
deniskuzZ
changed the title
deniskuzZ
changed the title
deniskuzZ
force-pushed
the
vectorization_fix
branch
from
ad0fb37
to
9d10b94
Compare
asf-ci-hive
added
tests pending
tests unstable
and removed
tests unstable
tests pending
labels
|
LGTM |
…tAndSchemaEvolution
deniskuzZ
force-pushed
the
vectorization_fix
branch
from
9d10b94
to
811ce1f
Compare
|
soumyakanti3578
approved these changes
Nov 4, 2024
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?
Bug-Fix
Why are the changes needed?
Disabled vectorization:
enabledConditionsNotMet: Could not enable vectorization due to partition column names size 1 is greater than the number of table column names size 0 IS false
Does this PR introduce any user-facing change?
No
Is the change a dependency upgrade?
No
How was this patch tested?
qtests