[
https://issues.apache.org/jira/browse/HADOOP-14154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16551453#comment-16551453
]
Steve Loughran commented on HADOOP-14154:
-----------------------------------------
when the patch goes in, this doc needs to be in the s3guard docs as markdown
somehow; maybe a whole new doc
* spelling of "isAuthoratitave" wrong at the bottom of p1
* compatibility: what happens if old client does a listing and updates a new
DB? Will the old value be retained? Presumably its implicit that no
is_authoritative column means: !is_authoritative
This patch nice as its update strategy is simple: writes from new clients add
the column. It does mean that if you run the new client against an old table
the old table gets updated, but that's ok, provided the next listing by an old
client deletes that isAuth bit. If the bit remained set while things got
updated by an old client, you could be in trouble
> 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
>
>
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
