[
https://issues.apache.org/jira/browse/HDDS-10640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17851924#comment-17851924
]
Ivan Andika commented on HDDS-10640:
------------------------------------
> {{If the ETag does not contain the number of MPU part (e.g. legacy MPU key),
> don't return the response header.}}
What is the format of this ETag? How is it different from the ETag with MPU in
it?
[~sarvekshayr] Thanks for working on this. Just checked the ETag patch
[https://github.com/apache/ozone/pull/5162] again (specifically
S3MultipartUploadCompleteRequest), I think my previous description is not
accurate, the legacy MPU key will not have ETag, so I think just need to return
the header only if the ETag metadata exists. I think there is no case where the
ETag of MPU key has different format, but I might be forgetting something.
[~vtutrinov] might help to confirm.
> Support x-amz-mp-parts-count for MPU key
> ----------------------------------------
>
> Key: HDDS-10640
> URL: https://issues.apache.org/jira/browse/HDDS-10640
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: S3, s3gateway
> Reporter: Ivan Andika
> Assignee: Sarveksha Yeshavantha Raju
> Priority: Minor
> Labels: GoodForNewContributors, newbie
>
> Description: The count of parts this object has. This value is only returned
> if you specify {{partNumber}} in your request and the object was uploaded as
> a multipart upload.
> Reference:
> [https://docs.aws.amazon.com/AmazonS3/latest/API/API_HeadObject.html]
> [https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html]
> Possible implementation: Since ETag of MPU key suffix is the number of the
> parts in the MPU, we can use that instead. If the ETag does not contain the
> number of MPU part (e.g. legacy MPU key), don't return the response header.
> Should be tested using unit tests and acceptance tests.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
