You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Samarth Jain (JIRA)" <ji...@apache.org> on 2016/12/06 21:37:59 UTC

[jira] [Commented] (PHOENIX-3520) Store metadata for tenant views in a separate column family

    [ 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)