You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2016/11/29 15:49:58 UTC
[jira] [Created] (HADOOP-13843) S3Guard, MetadataStore to support
atomic create(path, overwrite=false)
Steve Loughran created HADOOP-13843:
---------------------------------------
Summary: S3Guard, MetadataStore to support atomic create(path, overwrite=false)
Key: HADOOP-13843
URL: https://issues.apache.org/jira/browse/HADOOP-13843
Project: Hadoop Common
Issue Type: Sub-task
Components: fs/s3
Affects Versions: 3.0.0-alpha2
Reporter: Steve Loughran
Support atomically enforced file creation. Current s3a can do a check in create() and fail if there is something there, but a new entry only gets created at the end of the PUT; during the entire interval between that check and the close() of the stream, there's nothing to stop other callers creating an object.
Proposed: s3afs can do a check + create a 0 byte file at the path; that'd need some {{putNoOverwrite(DirListingMetadata)}} call in MetadataStore, followed by a PUT of an 0-byte file to S3. That will increase cost of file creation, though at least with the MD store, the cost of the initial getFileStatus() check is down.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org