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 081DA200C1A for ; Mon, 13 Feb 2017 13:22:19 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 0691F160B60; Mon, 13 Feb 2017 12:22:19 +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 4C295160B4D for ; Mon, 13 Feb 2017 13:22:18 +0100 (CET) Received: (qmail 35539 invoked by uid 500); 13 Feb 2017 12:20:14 -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 32203 invoked by uid 99); 13 Feb 2017 12:20:08 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Feb 2017 12:20:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id E1F6CC0D56 for ; Mon, 13 Feb 2017 12:20:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.199 X-Spam-Level: X-Spam-Status: No, score=-1.199 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, 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 (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 1QV4sEN6nH6O for ; Mon, 13 Feb 2017 12:20:07 +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 5534C61318 for ; Mon, 13 Feb 2017 12:19:30 +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 6BA0DE069F for ; Mon, 13 Feb 2017 12:19:20 +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 A8F2522706 for ; Mon, 13 Feb 2017 11:07:41 +0000 (UTC) Date: Mon, 13 Feb 2017 11:07:41 +0000 (UTC) From: "Bhupendra Kumar Jain (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-17635) enable_table_replication script cannot handle replication scope MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 13 Feb 2017 12:22:19 -0000 [ https://issues.apache.org/jira/browse/HBASE-17635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15863476#comment-15863476 ] Bhupendra Kumar Jain commented on HBASE-17635: ---------------------------------------------- HBASE-17460 skips the replication scope attribute comparison while comparing descriptors. I think that should resolve this. > enable_table_replication script cannot handle replication scope > --------------------------------------------------------------- > > Key: HBASE-17635 > URL: https://issues.apache.org/jira/browse/HBASE-17635 > Project: HBase > Issue Type: Bug > Components: Replication > Affects Versions: 1.3.1 > Reporter: Lars George > > When you add a peer, then enable a table for replication using {{enable_table_replication}}, the script will create the table on the peer cluster, but with one difference: > _Master Cluster_: > {noformat} > hbase(main):027:0> describe 'testtable' > Table testtable is ENABLED > testtable > COLUMN FAMILIES DESCRIPTION > {NAME => 'cf1', DATA_BLOCK_ENCODING => 'NONE', BLOOMFILTER => 'ROW', REPLICATION_SCOPE => '1', VERSIONS => '1', COMPRESSION => 'NONE', MIN_VERSIONS => '0', TTL => 'FOREVER', KEEP_DELETED_CELLS => 'FALSE', > BLOCKSIZE => '65536', IN_MEMORY => 'false', BLOCKCACHE => 'true'} > 1 row(s) in 0.0700 seconds > {noformat} > _Peer Cluster_: > {noformat} > hbase(main):003:0> describe 'testtable' > Table testtable is ENABLED > testtable > COLUMN FAMILIES DESCRIPTION > {NAME => 'cf1', DATA_BLOCK_ENCODING => 'NONE', BLOOMFILTER => 'ROW', REPLICATION_SCOPE => '0', COMPRESSION => 'NONE', VERSIONS => '1', TTL => 'FOREVER', MIN_VERSIONS => '0', KEEP_DELETED_CELLS => 'FALSE', > BLOCKSIZE => '65536', IN_MEMORY => 'false', BLOCKCACHE => 'true'} > 1 row(s) in 0.1260 seconds > {noformat} > Note that the replication scope is different. Removing the peer, adding it again and enabling the table gives this now: > {noformat} > hbase(main):026:0> enable_table_replication 'testtable' > ERROR: Table testtable exists in peer cluster 1, but the table descriptors are not same when compared with source cluster. Thus can not enable the table's replication switch. > {noformat} > That is dumb, as it was the same script that enabled the replication scope in the first place. It should skip that particular attribute when comparing the cluster schemas. -- This message was sent by Atlassian JIRA (v6.3.15#6346)