vtutrinov opened a new pull request, #5668: URL: https://github.com/apache/ozone/pull/5668
## What changes were proposed in this pull request? Replace the uploaded part's path with its content md5 hash for the part's ETag response field In the scope of the [HDDS-9115](https://issues.apache.org/jira/browse/HDDS-9115) [HDDS-9114](https://issues.apache.org/jira/browse/HDDS-9114) jira tickets the feature to store key's ETag (content md5 hash) was implemented. But the **ETag** field in the response of the part loading request wasn't changed and showed the part's path as it takes part in completeMultipartUpload request (OM). The PR contains the next changes: * replace path-representation of the part's ETag by its content md5 hash * update org.apache.hadoop.ozone.om.request.s3.multipart.S3MultipartUploadCommitPartRequest is the scope of parts validating - now we validate the part's ETag instead of its partName * add eTag field to OmClientProtocol.proto/MultipartCommitUploadPartResponse * add eTag field to OmClientProtocol.proto/Part (to make completeMultipartUpload request) * add eTag field to OmClientProtocol.proto/PartInfo (listParts) ## What is the link to the Apache JIRA https://issues.apache.org/jira/browse/HDDS-9115 ## How was this patch tested? Existing unit, integration, and smoke/acceptance/robot tests. The robot test **smoketest/s3/MutipartUpload.robot/"Test Multipart Upload Complete"** was patched to compare the part's ETag with md5 hash of their content -- 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]
