-
Notifications
You must be signed in to change notification settings - Fork 397
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
FinishCopyObject endpoint should accept new metadata #4483
Milestone
Comments
Change https://review.dev.storj.io/c/storj/common/+/6980 mentions this issue. |
storjBuildBot
pushed a commit
to storj/common
that referenced
this issue
Mar 3, 2022
storj/storj#4483 Change-Id: I671eff0d5483dcde7aa564d4e9c0a5b13de9ba35
Change https://review.dev.storj.io/c/storj/common/+/6990 mentions this issue. |
storjBuildBot
pushed a commit
to storj/common
that referenced
this issue
Mar 3, 2022
This will new field will give us ability to verify if destination object metadata should be preserved or overridden with newly provided. storj/storj#4483 Change-Id: Ib80f357584828fcafda410dbcca3da8a3448bf5a
Change https://review.dev.storj.io/c/storj/storj/+/6999 mentions this issue. |
dlamarmorgan
pushed a commit
that referenced
this issue
Oct 18, 2022
Copy object functionality should support setting new metadata for copy. This change is adjusting FinishCopyObject method to set new metadata when OverrideMetadata field is set to true. Fixes #4483 Change-Id: Ica37cb57e8edae301cdc483fbda4f3ddba5d2702
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While doing server-side copy object we need to support two ways of handling metadata:
This ticket is to support this second option and this is part of satellite implementation. Uplink implementation has a separate ticket storj/uplink#81.
The text was updated successfully, but these errors were encountered: