You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2016/06/16 20:02:05 UTC

[jira] [Created] (HADOOP-13282) S3 blob etags to be made visible in status/getFileChecksum() calls

Steve Loughran created HADOOP-13282:
---------------------------------------

             Summary: S3 blob etags to be made visible in status/getFileChecksum() calls
                 Key: HADOOP-13282
                 URL: https://issues.apache.org/jira/browse/HADOOP-13282
             Project: Hadoop Common
          Issue Type: Sub-task
          Components: fs/s3
            Reporter: Steve Loughran
            Priority: Minor


If the etags of blobs were exported via {{getFileChecksum() }}, it'd be possible to probe for a blob being in sync with a local file. Distcp could use this to decide whether to skip a file or not.

Now, there's a problem there: distcp needs source and dest filesystems to implement the same algorithm. It'd only work out the box if you were copying between S3 instances. There are also quirks with encryption and multipart: [s3 docs|http://docs.aws.amazon.com/AmazonS3/latest/API/RESTCommonResponseHeaders.html]. At the very least, it's something which could be used when indexing the FS, to check for changes later.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org