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

Aaron Fabbri edited comment on HADOOP-14154 at 8/9/17 3:56 PM:
---------------------------------------------------------------

Hi [~ste...@apache.org].  I have a prototype patch sitting around somewhere 
which implements authoritative listings for DynamoDB.  The solution is more 
complex than the original description here implies, so we should either rename 
this jira or create a new one.

Whichever JIRA we use, it should go in a Phase II umbrella for post-merge work.


was (Author: fabbri):
Hi [~ste...@apache.org].  I have a prototype patch sitting around somewhere 
which implements authoritative listings for DynamoDB.  The solution is more 
complex than the original description here implies, so we should either rename 
this jira or create a new one.

> Set isAuthoritative flag when creating DirListingMetadata in DynamoDBMetaStore
> ------------------------------------------------------------------------------
>
>                 Key: HADOOP-14154
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14154
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>            Reporter: Rajesh Balamohan
>            Priority: Minor
>         Attachments: HADOOP-14154-HADOOP-13345.001.patch, 
> HADOOP-14154-HADOOP-13345.002.patch
>
>
> Currently {{DynamoDBMetaStore::listChildren}} does not populate 
> {{isAuthoritative}} flag when creating {{DirListingMetadata}}. 
> This causes additional S3 lookups even when users have enabled 
> {{fs.s3a.metadatastore.authoritative}}.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
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