Mailing-List: contact dev-help@phoenix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@phoenix.apache.org
Date: Tue, 6 Dec 2016 21:37:59 +0000 (UTC)
From: "Samarth Jain (JIRA)" <jira@apache.org>
To: dev@phoenix.apache.org
Message-ID: <JIRA.13026131.1481060208000.454828.1481060279467@Atlassian.JIRA>
In-Reply-To: <JIRA.13026131.1481060208000@Atlassian.JIRA>
References: <JIRA.13026131.1481060208000@Atlassian.JIRA> <JIRA.13026131.1481060208403@arcas>
Subject: [jira] [Commented] (PHOENIX-3520) Store metadata for tenant views
 in a separate column family
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 06 Dec 2016 21:38:01 -0000


    [ https://issues.apache.org/jira/browse/PHOENIX-3520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15726787#comment-15726787 ] 

Samarth Jain commented on PHOENIX-3520:
---------------------------------------

[~jamestaylor], [~lhofhansl]

> Store metadata for tenant views in a separate column family 
> ------------------------------------------------------------
>
>                 Key: PHOENIX-3520
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3520
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Samarth Jain
>
> Instead of storing metadata related to views in the default column family "0", we should instead store it in a different column family in the SYSTEM.CATALOG table. This enables us to set separate properties for the view metadata, and specifically, REPLICATION_SCOPE. In our production clusters we have often run into metadata corruption because of unwanted records getting replicated from the peer cluster. Being able to set this property will help us nicely isolate data that needs to be replicated from data that doesn't need to be.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)