-
-
Notifications
You must be signed in to change notification settings - Fork 90
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
Restore unique IDs for partition-local stores #1805
Conversation
38ce69c
to
2b663bd
Compare
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.
This seems to be in decent shape already, I think with a little effort we can get this over the line with only one more iteration.
There are still a few TODOs and FIXMEs in the code that should probably all get resolved too.
c98e79a
to
7ce5a45
Compare
* Add offset/events fields into partition and partition synopsis flatbuffers. * Store info about ids in the meta index. * Add optional 'ids' field to query to query for specific ids.
Since the store already handles this case correctly, we can simply delegate these kinds of queries forward.
7ce5a45
to
21416e4
Compare
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.
Pair review with @lava and verified that all integration tests pass with the local segment store now.
📔 Description
Restore the ability to use offsets/ids when working with partition-local stores. This should also make it possible to use
vast explore
andvast get
in combination with custom store backends.📝 Checklist
🎯 Review Instructions
Review commit-by-commit. Some points worth considering:
optional<ids>
instead of ids, to distinguish between "no ids given" and "the empty set of ids requested"?