-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
coprocessor: support unique index scan #2526
Conversation
/rebuild |
let r1 = get_idx_range(TABLE_ID, INDEX_ID, 0, 1); // point get | ||
let r2 = get_idx_range(TABLE_ID, INDEX_ID, 1, 4); // range seek | ||
let r3 = get_idx_range(TABLE_ID, INDEX_ID, 4, 5); // point get | ||
let r4 = get_idx_range(TABLE_ID, INDEX_ID, 5, KEY_NUMBER + 1 as i64); // range seek |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems KEY_NUMBER
is defined as usize
let mut scanner = IndexScanExecutor::new(wrapper.scan, wrapper.ranges, store, true); | ||
|
||
for tid in 0..KEY_NUMBER { | ||
let handle = KEY_NUMBER - tid - 1; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The result should be order by handle
ascending since desc
in request is false.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@breeswish PTAL |
@coocood PTAL |
LGTM |
@AndreMouche Can we merge now? |
/run-integration-tests |
Use get interface when scanning unique index.
@AndreMouche PTAL