[
https://issues.apache.org/jira/browse/HBASE-9899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15408701#comment-15408701
]
Hudson commented on HBASE-9899:
-------------------------------
FAILURE: Integrated in HBase-Trunk_matrix #1355 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/1355/])
HBASE-9899 for idempotent operation dups, return the result instead of (stack:
rev 975f0dd958debcdd842a95f8e9f7458689414fbf)
*
hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestScannerHeartbeatMessages.java
* hbase-client/src/main/java/org/apache/hadoop/hbase/protobuf/ProtobufUtil.java
*
hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestMultiParallel.java
*
hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestIncrementsFromClientSide.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/Region.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
*
hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestFromClientSide.java
*
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/ServerNonceManager.java
*
hbase-server/src/test/java/org/apache/hadoop/hbase/client/HConnectionTestingUtility.java
*
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/RSRpcServices.java
> for idempotent operation dups, return the result instead of throwing conflict
> exception
> ---------------------------------------------------------------------------------------
>
> Key: HBASE-9899
> URL: https://issues.apache.org/jira/browse/HBASE-9899
> Project: HBase
> Issue Type: Improvement
> Reporter: Sergey Shelukhin
> Assignee: Guanghao Zhang
> Fix For: 2.0.0
>
> Attachments: HBASE-9899-v1.patch, HBASE-9899-v2.patch,
> HBASE-9899-v3.patch, HBASE-9899-v3.patch, HBASE-9899-v4.patch,
> HBASE-9899-v4.patch
>
>
> After HBASE-3787, we could store mvcc in operation context, and use it to
> convert the modification request into read on dups instead of throwing
> OperationConflictException.
> MVCC tracking will have to be aware of such MVCC numbers present. Given that
> scanners are usually relatively short-lived, that would prevent low watermark
> from advancing for quite a bit more time
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
