hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Nauroth (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HADOOP-13451) S3Guard: Implement access policy using metadata store as source of truth.
Date Fri, 09 Sep 2016 21:32:20 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-13451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Chris Nauroth resolved HADOOP-13451.
    Resolution: Invalid
      Assignee:     (was: Lei (Eddy) Xu)

As per discussion on HADOOP-13345, we've been able to simplify the previous notion of "policy"
to the point that it is no longer relevant to track this as a separate sub-task.  I am resolving
the issue.

> S3Guard: Implement access policy using metadata store as source of truth.
> -------------------------------------------------------------------------
>                 Key: HADOOP-13451
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13451
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>            Reporter: Chris Nauroth
> Implement an S3A access policy that provides strong consistency and improved performance
by using the metadata store as the source of truth for metadata operations.  In many cases,
this will allow S3A to short-circuit calls to S3.  Assuming shorter latency for calls to the
metadata store compared to S3, we expect this will improve overall performance.  With this
policy, a client may not be capable of reading data loaded into an S3 bucket by external tools
that don't integrate with the metadata store.  Users need to be made aware of this limitation.

This message was sent by Atlassian JIRA

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

View raw message