feat(storage): support replicate batch (aka remote write) #718
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.
Signed-off-by: Alex Chi [email protected]
What's changed and what's your intention?
See https://singularity-data.quip.com/JXxMAhxzBKmD/Shared-State-Shared-Index-and-Efficient-Joins for more details. Now we will support "replicate batch" in Hummock, so that executors can write a batch without uploading them to S3. This interface is
replicate_batch
inStateStore
.We also refactor a lot for Hummock shared buffer so that we don't need to clone keys. Previously,
Every write batch requires a copy. Now we will use Bytes across our system.
Checklist
Refer to a related PR or issue link (optional)