LogDb: Draft RFC on time index - #471
Open
hachikuji wants to merge 3 commits into
Open
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The sequence-based APIs are suitable for persistent consumers following a cursor that we would expect in pipeline use cases. However, these use cases are typically better served by Buffer. LogDb's benefit is its ability to maintain ordered logs across a wide range of keys. For dynamic log queries across keys, users will ultimately need to map time to sequence numbers. So we need a time index. This RFC suggests a simple approach. SlateDb gives us monotonic per-record time already. We add a global index within each segment which maps between sequence numbers and timestamps for records in that segment.