[
https://issues.apache.org/jira/browse/HADOOP-13345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15878821#comment-15878821
]
Steve Loughran commented on HADOOP-13345:
-----------------------------------------
I'm trying to run the tests against s3 frankfurt, failing as I've an older
table there, which I'll have to delete. Only here's the fun part, because the
version check is in {{DynamoDBMetadataStore.initialize()}}, and that gets
called by the CLI Destroy before metastore.destroy can be called, there's
currently no way to destroy a table of an incompatible s3guard version from the
CLI.
How about that version check is made a (secret) internal config option, and in
the destroy operation, that option is set so that the init code skips the
version check?
> S3Guard: Improved Consistency for S3A
> -------------------------------------
>
> Key: HADOOP-13345
> URL: https://issues.apache.org/jira/browse/HADOOP-13345
> Project: Hadoop Common
> Issue Type: New Feature
> Components: fs/s3
> Reporter: Chris Nauroth
> Assignee: Chris Nauroth
> Attachments: HADOOP-13345.prototype1.patch, s3c.001.patch,
> S3C-ConsistentListingonS3-Design.pdf, S3GuardImprovedConsistencyforS3A.pdf,
> S3GuardImprovedConsistencyforS3AV2.pdf
>
>
> This issue proposes S3Guard, a new feature of S3A, to provide an option for a
> stronger consistency model than what is currently offered. The solution
> coordinates with a strongly consistent external store to resolve
> inconsistencies caused by the S3 eventual consistency model.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
