[ 
https://issues.apache.org/jira/browse/HADOOP-13452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15505221#comment-15505221
 ] 

Aaron Fabbri commented on HADOOP-13452:
---------------------------------------

[~cnauroth] [~liuml07] I have a v2 patch that has roughly the same 
LocalMetadataStore code, but includes the changes we discussed: 
{{MetadataStore#initialize()}} takes a FileSystem, along with precondition 
checks that paths are absolute.

I'm thinking of submitting this patch and creating a new sub-JIRA for adding 
move() implementation and tests.  My preference is for smaller commits and code 
reviews, and move() could use its own.  

Would you rather get this v2 patch in, or wait until move() implementation is 
included? (I'm fine either way)


> S3Guard: Implement access policy for intra-client consistency with in-memory 
> metadata store.
> --------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-13452
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13452
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>            Reporter: Chris Nauroth
>            Assignee: Aaron Fabbri
>         Attachments: HADOOP-13452.001.patch
>
>
> Implement an S3A access policy based on an in-memory metadata store.  This 
> can provide consistency within the same client without needing to integrate 
> with an external system.



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

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

Reply via email to