Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C7414172DC for ; Fri, 20 Mar 2015 21:14:40 +0000 (UTC) Received: (qmail 92789 invoked by uid 500); 20 Mar 2015 21:14:40 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 92750 invoked by uid 500); 20 Mar 2015 21:14:40 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 92737 invoked by uid 99); 20 Mar 2015 21:14:40 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Mar 2015 21:14:40 +0000 Date: Fri, 20 Mar 2015 21:14:40 +0000 (UTC) From: "Sergey Shelukhin (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-9899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin updated HBASE-9899: ------------------------------------ Assignee: Enis Soztutar > 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: Enis Soztutar > > 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)