[ https://issues.apache.org/jira/browse/HBASE-8458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17054584#comment-17054584 ]
Toshihiro Suzuki edited comment on HBASE-8458 at 3/9/20, 1:10 AM: ------------------------------------------------------------------ [~gxcheng] This is a very useful feature. And we need it for our use case. Are you still work on it? Or Can I take it up? was (Author: brfrn169): [~gxcheng] This is a very useful feature. and we need it for our use case. Are you still work on it? Or Can I take it up? > Support for batch version of checkAndPut() and checkAndDelete() > --------------------------------------------------------------- > > Key: HBASE-8458 > URL: https://issues.apache.org/jira/browse/HBASE-8458 > Project: HBase > Issue Type: Improvement > Components: Client, regionserver > Affects Versions: 0.95.0 > Reporter: Hari Mankude > Assignee: Guangxu Cheng > Priority: Major > > 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 > checkAndPut() instead of a put(). However, doing a checkAndPut() rpc for > every key update is non optimal. It would be good to have a batch version of > checkAndPut() 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 checkAndPut() > Batch version of checkAndDelete() is a similar requirement. -- This message was sent by Atlassian Jira (v8.3.4#803005)