[
https://issues.apache.org/jira/browse/HBASE-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12830430#action_12830430
]
Andrew Purtell commented on HBASE-1728:
---------------------------------------
{quote}
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.
{quote}
Following up with the latter, a generic framework could e.g. read a class name
from a family attribute, instantiate that object to make replication/routing
decisions (via dynamic load from classpath using hdfs classloader, or using
coprocessors at some future time), hand each kv to the object via an interface
method, and use an int result as replication scope and priority as described
above. This is like mixing filters with replication and a priority queue. Some,
but not too much, additional work in return for affording users a lot of
function to build upon.
Note the framework can be flexible enough for someone to go even further and
encode destination as well as priority in the int and substitute their own
replication engine capable of complex routing even if we think that is out of
scope of core. We just need to make the right bits of the replication logic
subclassable.
> 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.
