[
https://issues.apache.org/jira/browse/HADOOP-13345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15925087#comment-15925087
]
Steve Loughran commented on HADOOP-13345:
-----------------------------------------
I've been thinking a bit about DDB table names in a large organisation. What
we've done today: table name == bucket name works for us developers, but I'm so
sure it will work in large orgs. Even in house I can see a trend for developers
like rajesh to use his name in tables to help assign ownership.
h4. What about the prefix "s3guard+" on all buckets unless otherwise stated?
That way, people looking at costs of AWS accounts can see which costs are due
to s3guard, without having to look into the tables, or search for matching
buckets of the same name...
> 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]
