hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-9899) for idempotent operation dups, return the result instead of throwing conflict exception
Date Mon, 01 Aug 2016 07:48:20 GMT

    [ https://issues.apache.org/jira/browse/HBASE-9899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15401668#comment-15401668
] 

Ted Yu commented on HBASE-9899:
-------------------------------

{code}
-      assert newResult.getState() == OperationContext.WAIT;
+      // assert newResult.getState() == OperationContext.WAIT;
{code}
Why was the assertion commented out ?

Can you add test for Append timing out ?

> 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, 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)

Mime
View raw message