hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guanghao Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-9899) for idempotent operation dups, return the result instead of throwing conflict exception
Date Mon, 24 Apr 2017 03:15:04 GMT

     [ https://issues.apache.org/jira/browse/HBASE-9899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Guanghao Zhang updated HBASE-9899:
----------------------------------
    Attachment: HBASE-9899-addendum-branch-1.patch

> 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, 1.3.0, 1.4.0
>
>         Attachments: HBASE-9899-addendum-branch-1.patch, HBASE-9899-addendum.patch, HBASE-9899-branch-1.patch,
HBASE-9899-branch-1.patch, HBASE-9899-branch-1.patch, 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.15#6346)

Mime
View raw message