[
https://issues.apache.org/jira/browse/HBASE-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12737392#action_12737392
]
Jim Kellerman commented on HBASE-1728:
--------------------------------------
I admit I haven't been following this closely (my other job keeps getting in
the way :(
However, from what I understand, scoping is currently either { local | global }
is that correct?
Do we envision other types of scoping?
If not, wouldn't a byte suffice instead of an int?
I understand that you are thinking that you were envisioning routing policies,
but in that case is an int enough to express that? I suppose the int could
select the routing policy, but realistically how many policies will there be?
2**32 - 1 ? It would be hard to imagine that there would be more than 127, so a
byte would suffice, and you could use the sign bit to indicate local or global.
In the Yahoo user database (UDB), we mostly wanted every user's data on every
server farm in the US, but we often restricted what international server farms
could replicate (or even access) data for users whose home locale was not
serviced by that international server farm. To handle that each farm had a name
(3-4 characters) and for replication outside the US, the farms that the user's
data was replicated to was just a list of farms. That meant that we only had to
send updates to those foreign farms if the user's data was present there.
Admittedly, this policy was specific to the UDB, but I wanted to share a
perspective of replication that came from my deep dark distant past.
FWIW.
> 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.
