Log based replication | Add copy object flow for versioned objects #7508
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.
Explain the changes
Note:
in the case of a few objects with the same prefix, all these objects up to a maximum of REPLICATION_MAX_KEYS (or 1000) will be processed and replicated.
e.g.
if we have an object name
test.text
and it have 3 versionsand if we also have
test1.text
andtest2.text
which also have few versions,and the log hints that
test.text
was written, all of those objects and their versions (up to 1000 as default) will be processed and replicated.Note 2:
in the case of sync-version, there will be no difference between copy and delete operations process.
This is because we still need to be aware of the version's history and may even do a copy before we do a delete (which should only be if the delete marker is the latest.)
Testing Instructions:
config.REPLICATION_ENABLED = false;