Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <10899814.1248996555108.JavaMail.jira@brutus>
Date: Thu, 30 Jul 2009 16:29:15 -0700 (PDT)
From: "ryan rawson (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Commented: (HBASE-1728) Column family scoping
In-Reply-To: <1462453048.1248995354982.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12737355#action_12737355 ] 

ryan rawson commented on HBASE-1728:
------------------------------------

thanks for making a start, here are 2 thoughts:

- if it goes in HCD, does that mean we have to take a table outage to enable/disable replication?  That might not be acceptable to some people (me included)
- we want to capture multiple replication destinations, with individual control over each one. Replication will eventually form the backbone of our DR and data analysis strategy, so we will be expecting to have multiple replication streams.

> Column family scoping
> ---------------------
>
>                 Key: HBASE-1728
>                 URL: https://issues.apache.org/jira/browse/HBASE-1728
>             Project: Hadoop HBase
>          Issue Type: Sub-task
>            Reporter: Andrew Purtell
>             Fix For: 0.21.0
>
>         Attachments: HBASE-1728.patch
>
>
> Support column family scoping via a new HCD attribute. Add convenience methods. Add Thrift, REST, and Stargate support. Provide initial set of scoping constants and javadoc setting expectations for a simple default binary scoping policy: replicate, or do not. Make the underlying type Integer so more complex edit routing policies are possible. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.