Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 42A7C200BBB for ; Thu, 27 Oct 2016 00:22:00 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 41675160AFD; Wed, 26 Oct 2016 22:22:00 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id A266C160B02 for ; Thu, 27 Oct 2016 00:21:59 +0200 (CEST) Received: (qmail 74178 invoked by uid 500); 26 Oct 2016 22:21:58 -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 73841 invoked by uid 99); 26 Oct 2016 22:21:58 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Oct 2016 22:21:58 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 701572C2A69 for ; Wed, 26 Oct 2016 22:21:58 +0000 (UTC) Date: Wed, 26 Oct 2016 22:21:58 +0000 (UTC) From: "stack (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-14465) Backport 'Allow rowlock to be reader/write' to branch-1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 26 Oct 2016 22:22:00 -0000 [ https://issues.apache.org/jira/browse/HBASE-14465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15609871#comment-15609871 ] stack commented on HBASE-14465: ------------------------------- Or rather [~apurtell], looking closer, how we lock changed (support for read/write) so the old API no longer makes sense (you cannot respect the old boolean of whether to wait for the lock -- probably why it was changed). A restore looks awkward. > Backport 'Allow rowlock to be reader/write' to branch-1 > ------------------------------------------------------- > > Key: HBASE-14465 > URL: https://issues.apache.org/jira/browse/HBASE-14465 > Project: HBase > Issue Type: Sub-task > Components: regionserver > Reporter: stack > Assignee: stack > Fix For: 1.2.0, 1.3.0 > > Attachments: 14465.branch-1.txt, 14465.branch-1.v2.txt, 14465.branch-1.v2.txt, 14465.branch-1.v2.txt, 14465.branch-1.v3.txt, 14465.branch-1.v3.txt, 14465.branch-1.v4.txt, 14465.branch-1.v4.txt, 14465.branch-1.v4.txt, 14465.branch-1.v5.txt, 14465.branch-1.v5.txt, 14465.branch-1.v9.txt, 14465.branch-1.v9.txt, 14465.branch-1.v9.txt, 14465.txt > > > Backport to branch-1. > You want this in 1.2 [~busbey]? Its cleanup and fixes a possible dataloss. On other hand, its a bit of refactoring. -- This message was sent by Atlassian JIRA (v6.3.4#6332)