Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Wed, 6 Nov 2013 00:44:20 +0000 (UTC)
From: "Sergey Shelukhin (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.12677693.1383698586421.25361.1383698660691@arcas>
In-Reply-To: <JIRA.12677693.1383698586421@arcas>
References: <JIRA.12677693.1383698586421@arcas>
Subject: [jira] [Created] (HBASE-9899) for idempotent operation dups, return
 the result instead of throwing conflict exception
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Sergey Shelukhin created HBASE-9899:
---------------------------------------

             Summary: 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


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.1#6144)