-
Notifications
You must be signed in to change notification settings - Fork 11
Add abstractions for tiered storage of stream data #196
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
the-mikedavis
wants to merge
4
commits into
rabbitmq:main
Choose a base branch
from
amazon-mq:tiered-storage-abstractions
base: main
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
4 commits
Select commit
Hold shift + click to select a range
78c02da
Add `osiris_log_reader` abstraction over offset readers
the-mikedavis f71db80
Add a `{'fun', fun()}` retention spec
the-mikedavis 3c76bb8
Expose `osiris_log:parse_header/2`
the-mikedavis 74e0258
Add `osiris_log_manifest` behaviour for hooks into log writers
the-mikedavis 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
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.
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.
The force pushes were to rebase and modify this retention spec. Before it was
Going through the sorted set of index files, you could return
trueto delete index+segment file pairs andfalseto stop evaluating the retention function.For retention where you want to keep some offset, though, this meant that you had to read the index file contents and a chunk from the segment too, since you don't know the final offset in the segment just from the index file. Passing the full list of index files lets us determine which files to keep and which to delete just from the index file names.
Here is where it's used in
rabbitmq_stream_s3to clean up any segments which have been fully uploaded to the remote tier and are not the current segment: https://github.com/amazon-mq/rabbitmq-stream-s3/blob/57d0a0a93bdb7d3da1e6f03f828e0dfce31019a6/src/rabbitmq_stream_s3_log_manifest.erl#L968-L1069