bharatviswa504 opened a new pull request #2411:
URL: https://github.com/apache/ozone/pull/2411
## What changes were proposed in this pull request?
I have verified with aws s3 end point when uploading same content for same
part, PartName is always same.
In AWS S3 case it is md5sum, as in ozone we don't generate based on md5sum,
to solve this issue temporarily we can use same partNames when a part upload is
override again. In Aws s3 cp case, file is divided in to parts, so in this case
content will be same, so it is expecting same ETag/PartName I beleive for now I
will provide a fix, to generate partNames in a predictable fashion to solve
this issue. (So, if same content/different content part names will still be
same for same part)
```
aws s3api upload-part --bucket b1-1993 --key mpu1 --part-number 1 --body
/tmp/part1 --upload-id
V7QlWzticX051N0BrQBAKAm.piipdYjHJ569P4aFAB5Ti_inSpvEyXS4cKEA7sHHendCFo5WOsmF.psmTMm7lFZMtsGw1e_iLyfXoD1KEhQ-
{
"ETag": "\"759e3a4738c1fefbcca31b232ac3ed69\""
}
bviswanadham@MacBook-Pro target % aws s3api upload-part --bucket b1-1993
--key mpu1 --part-number 1 --body /tmp/part1 --upload-id
V7QlWzticX051N0BrQBAKAm.piipdYjHJ569P4aFAB5Ti_inSpvEyXS4cKEA7sHHendCFo5WOsmF.psmTMm7lFZMtsGw1e_iLyfXoD1KEhQ-
{
"ETag": "\"759e3a4738c1fefbcca31b232ac3ed69\""
}
```
## What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-5005
## How was this patch tested?
Updated tests
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
