Gabor Bota commented on HADOOP-14154:

* I've uploaded HADOOP-14154.004.patch with the tests for backward 
compatibility check for the translation 
({{testIsAuthoritativeCompatibilityItemToPathMetadata}} and 
* Added the modification to the md docs, that 
{{org.apache.hadoop.fs.s3a.s3guard.DynamoDBMetadataStore}} is capable for 
authoritative bit support.
* Tested against eu-west-1, and got known issues (testDestroyNoBucket).

I'll upload performance test results from an instance running on aws soon.

> Persist isAuthoritative bit in DynamoDBMetaStore (authoritative mode support)
> -----------------------------------------------------------------------------
>                 Key: HADOOP-14154
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14154
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>    Affects Versions: 3.0.0-beta1
>            Reporter: Rajesh Balamohan
>            Assignee: Gabor Bota
>            Priority: Minor
>         Attachments: HADOOP-14154-HADOOP-13345.001.patch, 
> HADOOP-14154-HADOOP-13345.002.patch, HADOOP-14154-spec-001.pdf, 
> HADOOP-14154-spec-002.pdf, HADOOP-14154.001.patch, HADOOP-14154.002.patch, 
> HADOOP-14154.003.patch, HADOOP-14154.004.patch, perf-eval-v1.diff, 
> run-dir-perf-itest.sh
> Add support for "authoritative mode" for DynamoDBMetadataStore.
> The missing feature is to persist the bit set in 
> {{DirListingMetadata.isAuthoritative}}. 
> This topic has been super confusing for folks so I will also file a 
> documentation Jira to explain the design better.
> We may want to also rename the DirListingMetadata.isAuthoritative field to 
> .isFullListing to eliminate the multiple uses and meanings of the word 
> "authoritative".

This message was sent by Atlassian JIRA

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