[
https://issues.apache.org/jira/browse/HADOOP-9565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14584501#comment-14584501
]
Steve Loughran commented on HADOOP-9565:
----------------------------------------
I don't know about {{.COPYING}}. that's not done in the swiftfs itself, it's
distcp/CLI
rename: same thing.
distcp assumes that directory rename is atomic and fast, so does a copy with
the suffix COPYING so that the (slow) upload can take place bit by bit. When
the upload is finished it does a quick rename() , only in swift and s3 that
rename is in fact a second copy.
the fix here is for distcp & fs cli to recognise object stores and act
differently, or adding an explicit 'don't rename" option for all object stores.
> Add a Blobstore interface to add to blobstore FileSystems
> ---------------------------------------------------------
>
> Key: HADOOP-9565
> URL: https://issues.apache.org/jira/browse/HADOOP-9565
> Project: Hadoop Common
> Issue Type: Improvement
> Components: fs, fs/s3, fs/swift
> Affects Versions: 2.6.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Labels: BB2015-05-TBR
> Attachments: HADOOP-9565-001.patch, HADOOP-9565-002.patch,
> HADOOP-9565-003.patch
>
>
> We can make the fact that some {{FileSystem}} implementations are really
> blobstores, with different atomicity and consistency guarantees, by adding a
> {{Blobstore}} interface to add to them.
> This could also be a place to add a {{Copy(Path,Path)}} method, assuming that
> all blobstores implement at server-side copy operation as a substitute for
> rename.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
