[
https://issues.apache.org/jira/browse/HBASE-10126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13846249#comment-13846249
]
Feng Honghua commented on HBASE-10126:
--------------------------------------
bq.So making this the default is probably not a good idea.
this is not made default, default is still the previous logic(try best but not
require to get all row-locks to proceed), see the change:
{code}
public void batch(final List<?extends Row> actions, final Object[] results)
throws InterruptedException, IOException {
batch(actions, results, false);
}
public void batch(final List<?extends Row> actions, final Object[] results,
boolean intraRegionAtomic)
throws InterruptedException, IOException {
connection.processBatch(actions, tableName, pool, results,
intraRegionAtomic);
}
{code}
> guarantee atomicity of multi-row mutation within a same region from a single
> HTable.batch
> -----------------------------------------------------------------------------------------
>
> Key: HBASE-10126
> URL: https://issues.apache.org/jira/browse/HBASE-10126
> Project: HBase
> Issue Type: Improvement
> Components: regionserver
> Reporter: Feng Honghua
> Assignee: Feng Honghua
> Attachments: HBASE-10126-0.94-v0.patch
>
>
> We use this improvement together with
> DelimitedKeyPrefixRegionSplitPolicy.java to implement local secondary index
> without the help of coprocessor.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
