fix(select): use native after option for pagination on Tarantool 2.10+#491
Merged
fix(select): use native after option for pagination on Tarantool 2.10+#491
Conversation
vakhov
force-pushed
the
fix/select-pagination-native-after
branch
from
b27adc3 to
3418643
Compare
Contributor
|
I think we should move version updates in workflow and Makefile to separate PR because it's not a part of this feature. |
vakhov
force-pushed
the
fix/select-pagination-native-after
branch
from
3418643 to
c1a9e46
Compare
Contributor
Author
Thanks for the suggestion. Agreed. I’ve removed version updates from this PR and will put them into a separate PR. |
ita-sammann
approved these changes
Feb 10, 2026
vakhov
force-pushed
the
fix/select-pagination-native-after
branch
3 times, most recently
from
53e5b9b to
ca89634
Compare
Optimize crud.select() and crud.pairs() pagination with after cursor by using native after option on Tarantool 2.10+ for O(1) cursor positioning instead of O(N) scroll_to_after_tuple. The optimization applies to all iterators (GT/GE/LT/LE/EQ/REQ). For EQ/REQ iterators, native after is used only when after_tuple key matches scan_value to avoid 'Iterator position is invalid' error. Readview operations use native after only on Tarantool 3.x, since the after option for read_view:pairs() is not available in 2.x. Closes #488
vakhov
force-pushed
the
fix/select-pagination-native-after
branch
from
ca89634 to
e9e3b4e
Compare
Satbek
approved these changes
Feb 12, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Optimize crud.select() and crud.pairs() pagination with after cursor by using native
afteroption on Tarantool 2.10+ for O(1) cursor positioning instead of O(N) scroll_to_after_tuple.The optimization applies to all iterators (GT/GE/LT/LE/EQ/REQ). For EQ/REQ iterators, native after is used only when after_tuple key matches scan_value to avoid 'Iterator position is invalid' error.
Readview operations use native after only on Tarantool 3.x, since the after option for read_view:pairs() is not available in 2.x.
Closes #488