[
https://issues.apache.org/jira/browse/HBASE-1411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12708609#action_12708609
]
Andrew Purtell commented on HBASE-1411:
---------------------------------------
Andrew Purtell:
bq. I think HLogEdit would still be needed for something like HBASE-1295, for
noting the edit source so values are not re-replicated back to the peer.
stack:
bq. Can we do these markings as Types in the new KeyValue? Before serializing
we could AND the key type with source. How many bits do you need?
Andrew Purtell:
bq. I can't imagine more than 128 peer clusters for a replicator scenario, so 7
bits of Type would be enough, as long as they could be reserved somehow.
stack:
bq. Type is a byte only in KV. So, maximum you can have is 4, maybe 5 bits -
smile.
> remove HLogEdit
> ---------------
>
> Key: HBASE-1411
> URL: https://issues.apache.org/jira/browse/HBASE-1411
> Project: Hadoop HBase
> Issue Type: Improvement
> Reporter: Andrew Purtell
>
> From
> https://issues.apache.org/jira/browse/HBASE-1403?focusedCommentId=12708553&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12708553
> @stack:
> I'm thinking of the HLog and HCD. HLog values are a HLogEdit which is now
> just the new KeyValue class + a THBase flag. In interests of performance, I'd
> like to not have to create a HLogEdit at all and just shove in the KeyValue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
