hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-1728) Column family scoping
Date Sat, 06 Feb 2010 02:10:27 GMT

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

Andrew Purtell commented on HBASE-1728:
---------------------------------------

{quote}
 I don't see any reason why we should not at least first have only local or global scope.
{quote}
 
This is my thought as well for at first.

{quote}
 I'm not sure I agree that we should be able to set destinations on the family scope. What
kind of mess are you creating if all families from all tables are going different ways? 
{quote}

Well, the idea behind using an int for scoping, scoping at the family, and building kv routing
as a pluggable framework is to be generic enough to separate mechanism from policy. 

As for what we would build into core, I am thinking 1) simple binary scheme -- local or global;
and, possibly 2) extend the binary scheme such that, for example, a scope of 0 means local,
and a scope > 0 means global, with the desired priority of the replication set by the natural
ordering of the int.



> 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
>            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. 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.


Mime
View raw message