LowCardinality keys in set index #5154
Merged
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
KochetovNicolai
added
the
pr-bugfix
alexey-milovidov
approved these changes
Apr 30, 2019
proller
pushed a commit
that referenced
this pull request
May 13, 2019
…index LowCardinality keys in set index (cherry picked from commit d4b4a94)
proller
pushed a commit
that referenced
this pull request
May 13, 2019
…index LowCardinality keys in set index (cherry picked from commit d4b4a94)
proller
pushed a commit
that referenced
this pull request
May 13, 2019
…index LowCardinality keys in set index (cherry picked from commit d4b4a94)
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.
I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en
For changelog. Remove if this is non-significant change.
Category (leave one):
Short description (up to few sentences):
Fixed error
Set for IN is not created yetin case of using singleLowCardinalitycolumn in the left part of IN. This error happened ifLowCardinalitycolumn was the part of primary key. #5031