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 "Gabor Bota (JIRA)" <ji...@apache.org> on 2019/05/20 07:57:00 UTC
[jira] [Resolved] (HADOOP-14468) S3Guard: make short-circuit
getFileStatus() configurable
[ https://issues.apache.org/jira/browse/HADOOP-14468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gabor Bota resolved HADOOP-14468.
---------------------------------
Resolution: Fixed
Release Note: Resolved this with HADOOP-15999 : fix for OOB operations.
> S3Guard: make short-circuit getFileStatus() configurable
> --------------------------------------------------------
>
> Key: HADOOP-14468
> URL: https://issues.apache.org/jira/browse/HADOOP-14468
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.0.0-beta1
> Reporter: Aaron Fabbri
> Assignee: Gabor Bota
> Priority: Minor
>
> Currently, when S3Guard is enabled, getFileStatus() will skip S3 if it gets a result from the MetadataStore (e.g. dynamodb) first.
> I would like to add a new parameter {{fs.s3a.metadatastore.getfilestatus.authoritative}} which, when true, keeps the current behavior. When false, S3AFileSystem will check both S3 and the MetadataStore.
> I'm not sure yet if we want to have this behavior the same for all callers of getFileStatus(), or if we only want to check both S3 and MetadataStore for some internal callers such as open().
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org