[
https://issues.apache.org/jira/browse/HBASE-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12754817#action_12754817
]
Andrew Purtell commented on HBASE-1834:
---------------------------------------
The main problem I had with not doing it this way is getting to column family
metadata from various places in the code, for example
HLog.completeCacheFlush(). This was because I was trying to tag HLogKeys with
scope as they are written, and thus far scope information is kept in HCD.
However it doesn't have to be done that way. A replicator could look up what to
do for each KV according to information in the key. No HLogKey or KV would be
tagged with any scoping information. However byte[] compares for every KV would
be more overhead than modifying the write path to carry scope information
along.
Other options?
> Add scoping information to KVs
> ------------------------------
>
> Key: HBASE-1834
> URL: https://issues.apache.org/jira/browse/HBASE-1834
> Project: Hadoop HBase
> Issue Type: Sub-task
> Reporter: Andrew Purtell
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
