[
https://issues.apache.org/jira/browse/HADOOP-16190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated HADOOP-16190:
------------------------------------
Resolution: Duplicate
Status: Resolved (was: Patch Available)
I was about to tag this as for those versions of hadoop which don't pick up the
bigger HADOOP-16085 patch, but as that also includes handling for the special
case "AWS SDK xfer manager raises NPE on etag mismatch", I think we are better
off not doing this: its get complicated fast.
> S3A copyFile operation to include source versionID or etag in the copy request
> ------------------------------------------------------------------------------
>
> Key: HADOOP-16190
> URL: https://issues.apache.org/jira/browse/HADOOP-16190
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 2.9.2, 3.0.3
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Major
>
> The S3 {{CopyObjectRequest}} structure used to build a copy request takes,
> optionally
> * a version ID of the source file
> * the etag of the source file
> using these will guarantee that the source file is copied exactly once
> 1. When working with S3Guard in auth mode, and the etag/version are kept in
> the DDB table, that should be the authoritative source of metadata: fail fast
> if the file is out of date
> 2. And when non-auth mode is used, the getObjectMetadata check made should
> update the s3guard table if needed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
