You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Chao Chu (JIRA)" <ji...@apache.org> on 2016/06/27 06:56:52 UTC

[jira] [Commented] (HBASE-8458) Support for batch version of checkAndPut() and checkAndDelete()

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

Chao Chu commented on HBASE-8458:
---------------------------------

I am also interested in this issue. Having gone through all the comments above, it looks like we don't have a solution to achieve an equivalent of batch checkAndPut?

> 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
>
> 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
(v6.3.4#6332)