HIVE-29197: Disable vectorization for multi-column COUNT(DISTINCT) #6114
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
Indhumathi27
force-pushed
the
vect_distinct
branch
from
e75ce80 to
58d0528
Compare
asf-ci-hive
added
tests failed
tests pending
tests unstable
and removed
tests pending
tests failed
labels
Indhumathi27
force-pushed
the
vect_distinct
branch
from
58d0528 to
eb285e8
Compare
|
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?
Disabled vectorized execution for multi-column COUNT(DISTINCT) so queries fall back to row mode for unsupported expressions.
Why are the changes needed?
In case of query with filter on Partition column, and if the same column exists in count(distinct, col) udf, Partition column changes to constant.
Vectorized execution does not support multi-column COUNT(DISTINCT). This ensures queries run safely without exceptions.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Added test case