[ 
https://issues.apache.org/jira/browse/HBASE-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Daniel Cryans updated HBASE-1728:
--------------------------------------

    Description: Support column family scoping via a new HCD attribute. 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. Also identify every 
HLogKey with the original cluster's ID.  (was: 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. )
        Summary: Column family scoping and cluster identification  (was: Column 
family scoping)

I'm changing the title and description of this issue to reflect the new scope. 
We won't change stargate and thrift since replication is first added as a 
contrib. Also I'm bringing in the concept of cluster identification since that 
change is done around the exact same parts of the code.

> Column family scoping and cluster identification
> ------------------------------------------------
>
>                 Key: HBASE-1728
>                 URL: https://issues.apache.org/jira/browse/HBASE-1728
>             Project: Hadoop HBase
>          Issue Type: Sub-task
>            Reporter: Andrew Purtell
>            Assignee: Jean-Daniel Cryans
>             Fix For: 0.21.0
>
>         Attachments: HCD-family-scoping.patch, HLogKey-scoping.patch
>
>
> Support column family scoping via a new HCD attribute. 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. Also identify every 
> HLogKey with the original cluster's ID.

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

Reply via email to