[
https://issues.apache.org/jira/browse/HADOOP-13345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15799249#comment-15799249
]
Aaron Fabbri commented on HADOOP-13345:
---------------------------------------
Happy new year [[email protected]] and [~liuml07]. I'd like to figure out the
set of JIRAs we want to resolve before merging the feature branch. We've
discussed before targeting basic list consistency for the initial feature set.
It seems like the main features we need are:
Needed:
- Any DynamoDB bugs (initialization stuff, etc).
- Basic CLI functionality. HADOOP-13650
- Multi-bucket improvements, including read-only buckets. HADOOP-13876. I
think the solution will be to tackle the per-bucket config JIRA HADOOP-13336
Maybe:
- Make sure testing is sorted. Currently tests are good but a bit manual. Do
we want to do HADOOP-13589 pre merge?
Post merge:
- The rest of the JIRAs.
Let me know what you think. Should we create a new "s3guard phase 2" umbrella
JIRA so we can start moving stuff over once we have consensus?
> 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-ConsistentListingonS3-Design.pdf, S3GuardImprovedConsistencyforS3A.pdf,
> S3GuardImprovedConsistencyforS3AV2.pdf, s3c.001.patch
>
>
> 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.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
