[
https://issues.apache.org/jira/browse/HBASE-18962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16280055#comment-16280055
]
Umesh Agashe edited comment on HBASE-18962 at 12/6/17 11:36 AM:
----------------------------------------------------------------
[~chancelq], Yes, as you have posted the code, doBatchOp() method sets the
index. Currently methods doNonAtomicRegionMutation() in server use
addResultOrException() and that is what client expects. Will using
setException() instead need client changes?
was (Author: uagashe):
Yes, as you have posted the code, doBatchOp() methods sets the index. Currently
methods doNonAtomicRegionMutation() in server use addResultOrException() and
that is what client expects. Will using setException() instead need client
changes?
> Support atomic BatchOperations through batchMutate()
> ----------------------------------------------------
>
> Key: HBASE-18962
> URL: https://issues.apache.org/jira/browse/HBASE-18962
> Project: HBase
> Issue Type: Sub-task
> Components: regionserver
> Affects Versions: 2.0.0-alpha-3
> Reporter: Umesh Agashe
> Assignee: Umesh Agashe
> Fix For: 2.0.0-beta-1
>
> Attachments: hbase-18962.master.001.patch,
> hbase-18962.master.002.patch, hbase-18962.master.003.patch,
> hbase-18962.master.004.patch
>
>
> Support all mutations in BatchOperations to be applied atomically (all or
> none) by locking all rows corresponding to mutations exclusively.
> mutateRows() which uses MultiRowMutationProcessor applies all mutations
> atomically and batchMutate() is non-atomic. To unify code paths, isAtomic()
> attribute can be added to BatchOperations.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
