[
https://issues.apache.org/jira/browse/HBASE-9899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15401588#comment-15401588
]
Guanghao Zhang commented on HBASE-9899:
---------------------------------------
It seems not ralated. This patch just read mvcc number from WriteEntry and it
didn't change the read/write point directly. This failed ut passed in my local
machine and I can't reproduce this failure. Let the hadoop QA run again to see
whether it failed.
> 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
> Attachments: HBASE-9899-v1.patch, HBASE-9899-v2.patch,
> HBASE-9899-v3.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)
