feat(media): include payload keys in upload records - #4016
Closed
bradseiler wants to merge 1 commit into
Closed
Conversation
Co-authored-by: npub128x7j3pwgm4vs8yra3c42fcgcwcvh94g3luwzkqa376du2q6l0esqcrwch <51cde9442e46eac81c83ec71552708c3b0cb96a88ff8e1581d8fb4de281afbf3@buzz.block.builderlab.xyz> Signed-off-by: npub128x7j3pwgm4vs8yra3c42fcgcwcvh94g3luwzkqa376du2q6l0esqcrwch <51cde9442e46eac81c83ec71552708c3b0cb96a88ff8e1581d8fb4de281afbf3@buzz.block.builderlab.xyz>
bradseiler
force-pushed
the
seiler/media-upload-record-keys
branch
from
July 31, 2026 23:43
aae4515 to
106166b
Compare
Author
|
Superseded by consolidated PR #4533, which includes the full phased read/write policy and Kubernetes-runnable backfill and legacy-deletion tools. |
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
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.
Summary
Add the exact payload object key to media upload records as an optional additive field. Existing consumers can continue deriving the legacy key from
sha256andext; tolerant consumers can preferblob_keybefore sharded writes begin.Related issue
Stacked on #4015; requested in the linked Buzz channel thread.
Testing
bin/cargo test -p buzz-media(110 passed, 1 live-MinIO test ignored)bin/cargo clippy -p buzz-media --all-targets -- -D warningsbin/cargo fmt --checkStack