[
https://issues.apache.org/jira/browse/HADOOP-13452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15415488#comment-15415488
]
Chris Nauroth edited comment on HADOOP-13452 at 8/10/16 4:01 PM:
-----------------------------------------------------------------
[~fabbri], awesome, thank you for picking this up.
I have been thinking that the refactoring in HADOOP-13447 is a pre-requisite
for all of the "implement access policy" sub-tasks like this one.
Specifically, I expect the scope of each "implement access policy" sub-task is
to implement a new concrete subclass of {{AbstractS3AccessPolicy}}, with each
one implementing the different configurable semantics (e.g. in-memory vs.
strong consistency checks against the metadata store vs. "fully cached"
directories, etc.).
Please let me know whether or not this makes sense. Any opinions or code
review feedback on HADOOP-13447 are welcome, because it's a large refactoring.
was (Author: cnauroth):
[~fabbri], awesome, thank you for picking this up.
I have been thinking that the refactoring in HADOOP-13447 is a pre-requisite
for all of the "implement access policy" sub-tasks like this one.
Specifically, I expect the scope of each "implement access policy" sub-task is
to implement a new concrete subclass of {{AbstractS3AccessPolicy}}, with each
one implementing the different configurable semantics (e.g. in-memory vs.
strong consistency checks against the metadata store vs. "fully cached"
directories, etc.).
Please let me know whether or not this makes sense. Any opinions or code
review feedback on HADOOP-13446 are welcome, because it's a large refactoring.
> 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
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
