cherry-pick index related commits to 1.1-dev #14499
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
…14424) For composite index like `idx(col1, col2, col3)`, it should be possible to apply this index on equi-conditions like `col1 = 1 and col2 = 2`, if the selectivity is low enough. Approved by: @badboynt1
memtable is not sorted by primary keys Approved by: @m-schen, @ouyuanning
aunjgr
requested review from
m-schen,
ouyuanning and
badboynt1
as code owners
m-schen
approved these changes
Feb 1, 2024
sukki37
approved these changes
Feb 1, 2024
ouyuanning
approved these changes
Feb 1, 2024
sukki37
added a commit
that referenced
this pull request
Feb 2, 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 type of PR is this?
Which issue(s) this PR fixes:
issue #12517
What this PR does / why we need it:
rows in memtable are not sorted by primary keys