-
Notifications
You must be signed in to change notification settings - Fork 2.1k
feat(cubestore): Support QUEUE ADD_AND_RETRIEVE command #11590
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
Open
ovr
wants to merge
7
commits into
master
Choose a base branch
from
queue-add-immediate-acquire
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
6fecf52
feat(cubestore): QUEUE ADD_AND_RETRIEVE command
ovr 3d7bb9f
chore(cubestore): drop comments which repeat the implementation
ovr 7a54bee
docs(query-orchestrator): queue diagrams + fast track
ovr 2f53dab
feat(cubestore): bound the priority inversion of ADD_AND_RETRIEVE
ovr b62a000
test(cubestore): QUEUE ADD_AND_RETRIEVE backlog guard over SQL
ovr fe6380e
chore(cubestore): stop restating the claim rule in doc comments
ovr ab917ac
Update packages/cubejs-query-orchestrator/DEVELOPMENT.md
ovr File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Large diffs are not rendered by default.
Oops, something went wrong.
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
Nit, test strength: the numeric path suffixes make
key == idfor every item, so this assertion can't tell thekeyandidcolumns apart.QUEUE ACTIVEreturns(key, id, status, extra)— swap those two columns in the SQL layer and this test still passes, and so doesqueue_add_and_retrieve_row("4", true, 3, Some("4"), ...)above (idandactiveare also both"4").The pre-existing
queue_retrieve_extendedtest avoids this by using a non-numeric key (tests.rs:11544-11546: key"queue_key_3", id"3"). Naming the pathsSTANDALONE#queue:key1…:key4here costs nothing and makes the columns distinguishable — worth it sinceADD_AND_RETRIEVEis the command that newly reportsactivealongsideidin one row.Also minor:
assert_queue_add_and_retrieve_columnsis called on the first response but not on the second (tests.rs:12176). Since the second is the claimed case — the one whose column set the driver will actually read — it's the more useful of the two to pin.