[ 
https://issues.apache.org/jira/browse/HADOOP-13345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15647834#comment-15647834
 ] 

Steve Loughran commented on HADOOP-13345:
-----------------------------------------

thanks: sorry for breaking things —it's the price of working against a changing 
part of the codebase. Now I'm involved in this branch as well (a) I'll have 
less time to break things on branch-2 and (b) I'll be more aware of what I've 
just broken.

FWIW I don't think you need to do rebase here, merging is better for 
collaboration, and avoids that hell of having to fix up some patch conflict 
over a class you know gets deleted later. When this gets pulled into 
trunk/branch-2, it'll be done as a squashed merge, so there's no harm in doing 
merges here rather than rebase

> 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]

Reply via email to