refactor: remove sequence number from ScanRequest #2785
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
Signed-off-by: Ruihang Xia <[email protected]>
evenyag
approved these changes
Nov 21, 2023
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## develop #2785 +/- ##
===========================================
- Coverage 84.47% 84.12% -0.35%
===========================================
Files 728 728
Lines 113352 113349 -3
===========================================
- Hits 95756 95358 -398
- Misses 17596 17991 +395 |
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.
I hereby agree to the terms of the GreptimeDB CLA
What's changed and what's your intention?
Remove yet another overdesign.
Remove the sequence number from
ScanRequest. We won't be using it in the near future.Checklist
Refer to a related PR or issue link (optional)