You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Chris Nauroth (JIRA)" <ji...@apache.org> on 2016/08/02 00:13:21 UTC
[jira] [Updated] (HADOOP-13451) S3Guard: Implement access policy
using metadata store as source of truth.
[ https://issues.apache.org/jira/browse/HADOOP-13451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Nauroth updated HADOOP-13451:
-----------------------------------
Priority: Major (was: Minor)
> 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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org