[ https://issues.apache.org/jira/browse/HBASE-8458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17132894#comment-17132894 ]
Toshihiro Suzuki commented on HBASE-8458: ----------------------------------------- [~elserj] Thank you very much! {quote} I see this is tagged for 2.4.0 – is there appetite to cherry-pick this back to branch-2 as well? {quote} Yes, I will work on doing that. {quote} Could you write some release notes and then resolve this, Toshihiro Suzuki? {quote} Sure. After woking on branch-2, will do that. Thanks. > Support for batch version of checkAndMutate() > --------------------------------------------- > > Key: HBASE-8458 > URL: https://issues.apache.org/jira/browse/HBASE-8458 > Project: HBase > Issue Type: New Feature > Components: Client, regionserver > Reporter: Hari Mankude > Assignee: Toshihiro Suzuki > Priority: Major > Fix For: 3.0.0-alpha-1, 2.4.0 > > > The use case is that the user has multiple threads loading hundreds of keys > into a hbase table. Occasionally there are collisions in the keys being > uploaded by different threads. So for correctness, it is required to do > checkAndMutate() instead of a put(). However, doing a checkAndMutate() rpc > for every key update is non optimal. It would be good to have a batch version > of checkAndMutate() similar to batch put(). The client can partition the keys > on region boundaries. > The jira is NOT looking for any type of cross-row locking or multi-row > atomicity with checkAndMutate(). -- This message was sent by Atlassian Jira (v8.3.4#803005)