[
https://issues.apache.org/jira/browse/HADOOP-13345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15876515#comment-15876515
]
Aaron Fabbri commented on HADOOP-13345:
---------------------------------------
Sorry for delayed response..
{quote}
org.apache.hadoop.fs.s3a.ITestS3GuardListConsistency fails before/after merge.
Do I need to configure something special?
{quote}
You should not have to.
Strange, it has been working for me. Could be a difference in the tables we
use. I will run that test on the latest code now and see what happens. Could
be related to HADOOP-14096, which just got fixed.
{quote}We don't really change anything in that part. I guess the reason is
that, when enabling S3Guard, the code path that fails in S3AFileSystem changes
for that test somehow.
{quote}
Ok.. I'm wondering if that fix should be a separate commit instead of modifying
the merge commit? Maybe ping [[email protected]] for his opinion.
> 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]
