hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8458) Support for batch version of checkAndPut() and checkAndDelete()
Date Mon, 30 Dec 2013 20:37:51 GMT

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

Andrew Purtell commented on HBASE-8458:
---------------------------------------

bq. Keep the old API in 0.94 and 0.96 (or only do this in 0.98+ and remove the old API)

Sure, if something is available in the next week or so we can pull it in to 0.98 _and_ remove
the old API, presuming the new CheckAndRowMutation can go into 0.96 and the old APIs are marked
deprecated there. Otherwise a removal will have to wait for the next.

> 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.1.5#6160)

Mime
View raw message