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 8F2F3200C24 for ; Thu, 9 Feb 2017 00:50:45 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 8DE94160B67; Wed, 8 Feb 2017 23:50:45 +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 E2072160B49 for ; Thu, 9 Feb 2017 00:50:44 +0100 (CET) Received: (qmail 47389 invoked by uid 500); 8 Feb 2017 23:50:44 -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 47378 invoked by uid 99); 8 Feb 2017 23:50:44 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Feb 2017 23:50:44 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 9C7DA1A01DC for ; Wed, 8 Feb 2017 23:50:43 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id g-YTjefuDZbv for ; Wed, 8 Feb 2017 23:50:43 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id AAE155F589 for ; Wed, 8 Feb 2017 23:50:42 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 1BAE8E031F for ; Wed, 8 Feb 2017 23:50:42 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id C778D2528B for ; Wed, 8 Feb 2017 23:50:41 +0000 (UTC) Date: Wed, 8 Feb 2017 23:50:41 +0000 (UTC) From: "Vladimir Rodionov (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-16571) Consider locking target table(s) during restore operation MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 08 Feb 2017 23:50:45 -0000 [ https://issues.apache.org/jira/browse/HBASE-16571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Rodionov updated HBASE-16571: -------------------------------------- Fix Version/s: HBASE-7912 > Consider locking target table(s) during restore operation > --------------------------------------------------------- > > Key: HBASE-16571 > URL: https://issues.apache.org/jira/browse/HBASE-16571 > Project: HBase > Issue Type: Improvement > Reporter: Ted Yu > Labels: backup > Fix For: HBASE-7912 > > > During review of HBASE-15565, Stephen suggested taking table lock(s) on target table(s) during restore operation. > This would prevent admin from making accidental schema changes. -- This message was sent by Atlassian JIRA (v6.3.15#6346)