[
https://issues.apache.org/jira/browse/HBASE-8458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17175885#comment-17175885
]
Nick Dimiduk commented on HBASE-8458:
-------------------------------------
[~brfrn169] instead of pasting the javadoc, maybe we can link off to the API
docs? It's a little tricky because those docs haven't been released yet, but we
expect the root path the be consistent across releases.
Alternatively, you can paste sample code here, but use markdown format. Jira
doesn't process the content of that field, instead it's handled by Yetus and a
markdown generator.
> 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)
