[
https://issues.apache.org/jira/browse/HADOOP-13345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15390915#comment-15390915
]
Mingliang Liu commented on HADOOP-13345:
----------------------------------------
Thanks for addressing the comments, [~cnauroth]. I like the design and look
forward to its addressing the important S3A consistency problem in Hadoop.
{quote}
Are you recommending this based on the fact that the AWS SDK JavaDocs for
withKeyConditions describe it as a "legacy parameter", or is there something
more to it? This is my first time working with DynamoDB, so I'm learning as I
go.
{quote}
Sorry I don't have solid support. It stems from my personal experience when I
worked for DynamoDB. Key condition expression is a new and easier approach to
using expression-style syntax for specifying the key conditions. I searched and
found the official AWS blog
[here|https://aws.amazon.com/blogs/aws/dynamodb-update-improved-json-editing-key-condition-expressions/].
I then realized that the conditions of DDB requests are not that complex in
the current design. I now believe it's minor and can be improved later.
> 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,
> 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]
