[
https://issues.apache.org/jira/browse/HDDS-15182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fabian Morgan updated HDDS-15182:
---------------------------------
Status: Patch Available (was: In Progress)
> [STS] Remove latent extra read on CopyObject api - make CopyPart work
> similarly
> -------------------------------------------------------------------------------
>
> Key: HDDS-15182
> URL: https://issues.apache.org/jira/browse/HDDS-15182
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Fabian Morgan
> Assignee: Fabian Morgan
> Priority: Major
> Labels: pull-request-available
>
> In STS, CopyObject requires s3:GetObject action on source and s3:PutObject
> action on destination in order to successfully invoke the api. In the latent
> S3 implementation, the code was doing an additional read on the destination
> object to get the eTag and modificationTime when the file was created. This
> is problematic, because AWS doesn't require s3:GetObject action on the
> destination file, so this extra read was causing STS smoke tests to fail.
> In order to address, don't do the extra read (which will help performance as
> well) and instead make the commit key call return the modification time in
> the response and use that. Furthermore, the code already knows what the
> md5Hash/eTag is, so there is no need to read the destination object.
> For consistency, make uploadPartCopy similarly return the modification time
> as well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
