schema: correctly filtering and sorting on clustering columns. #37
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
dahankzter
force-pushed
the
invalid_range_queries
branch
from
a0238d4
to
8ca76c2
Compare
penberg
reviewed
Mar 21, 2019
penberg
reviewed
Mar 21, 2019
dahankzter
force-pushed
the
invalid_range_queries
branch
from
8ca76c2
to
04c0a00
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.
This PR adjusts the queries we execute on clustering keys. We used to try to restrict all the clustering keys to create ranges but this does not work. Only the last clustering key can be restricted in this way the others need to use
EQrestrictions.We should eventually ensure that we create all possible permutations of these queries. This PR only makes a small effort use some of the space available.
For more details see:
https://www.datastax.com/dev/blog/a-deep-look-to-the-cql-where-clause
Fixes: #36