hbase-issues mailing list archives

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

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

stack commented on HBASE-9899:
------------------------------

Sorry [~zghaobac]

This is a great patch. Very nice. I pushed to master. I tried backporting but lots of conflict.
Would you be up for having a go at it since you know this area well now? Else I'll give it
a go. Thanks.

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

Mime
View raw message