This repository has been archived by the owner on May 10, 2022. It is now read-only.
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.
feat: handle scan iteration exceed limit and refactor code #96
feat: handle scan iteration exceed limit and refactor code #96
Changes from 5 commits
ace4b88
8beba29
0efa8c6
7418797
c4ea4e4
962ce42
844302a
ed79081
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
What will happen if the server with scan-limit meets with the client of the previous version? Will the client throw an exception when it accepts
rocksdb::Status::kIncomplete
or just continue?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.
In current version, client will throw an exception when it accepts
rocksdb::Status::kIncomplete
immediately and can not get the result of the scanner. In this version, client will also throw an exception but will return scan result.