forked from cockroachdb/cockroach
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
70571: kvserver: add `RESUME_BYTE_LIMIT` and `RESUME_INTENT_LIMIT` r=nvanbenschoten,yuzefovich a=erikgrinaker This is essentially the two first commits from cockroachdb#68370, with some minor non-code tweaks. Splitting it off to work on cockroachdb#70564 in concert with cockroachdb#68370. ### roachpb: move `ResumeReason` enum out of `ResponseHeader` The `ResumeReason` enum constants won't necessarily be used only in the context of a response header, e.g. we want to return it from `MVCCScan` as well. This patch therefore moves the enum to the `roachpb` root. Release note: None ### kvserver: add `RESUME_BYTE_LIMIT` and `RESUME_INTENT_LIMIT` The `roachpb.ResumeReason` enum only contained the single reason `RESUME_KEY_LIMIT` (in addition to the `RESUME_UNKNOWN` zero value). This was outdated since iteration can be halted by byte limits and intent limits as well. This patch adds the new resume reasons `RESUME_BYTE_LIMIT` and `RESUME_INTENT_LIMIT`, adds `MVCCScanResult.ResumeReason` to plumb it through to the scan iteration, and updates relevant code. Release note: None Co-authored-by: Erik Grinaker <[email protected]>
- Loading branch information
Showing
18 changed files
with
817 additions
and
791 deletions.
There are no files selected for viewing
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
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
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
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
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
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
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
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
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
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
Oops, something went wrong.