-
Notifications
You must be signed in to change notification settings - Fork 241
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
Fix handling of archived object replacement #5678
Conversation
- The `delete` oplog entry must not be generated when putObject is used to restore the object: otherwise a GC request will be sent to cold backend, and the object will never be expired. - The `originOp` of the (new) metadata should not be affected: "s3:ReplaceArchivedObject" should only be set on the extra `delete` op in the oplog. Issue: CLDSRV-560
Hello francoisferrand,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
Incorrect fix versionThe
Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:
Please check the |
Issue: CLDSRV-560
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
|
/approve |
I have successfully merged the changeset of this pull request
The following branches have NOT changed:
Please check the status of the associated issue CLDSRV-560. Goodbye francoisferrand. The following options are set: approve |
delete
oplog entry must not be generated when putObject is usedto restore the object: otherwise a GC request will be sent to cold
backend, and the object will never be expired.
originOp
of the (new) metadata should not be affected:"s3:ReplaceArchivedObject" should only be set on the extra
delete
opin the oplog.
Issue: CLDSRV-560