[
https://issues.apache.org/jira/browse/HBASE-7233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13508973#comment-13508973
]
Matt Corgan commented on HBASE-7233:
------------------------------------
Not sure I follow everything so far, but I'm wondering if KeyValue should just
keep the Writable interface since KeyValue is the unit of input/output in
certain map-reduce jobs. The Cell interface improves on KeyValue when you are
passing around blobs of many Cells (since they can share common row-prefixes,
etc), but for map-reduce we are passing around individual Cells, so might as
well just keep using KeyValue. The Cells need to be standalone, so KeyValue
may be required.
Are there benefits to removing Writable for this particular class beyond
cleaning up the code? Maybe saving 4-8 bytes memory per KV in the memstore.
> Remove Writable Interface from KeyValue
> ---------------------------------------
>
> Key: HBASE-7233
> URL: https://issues.apache.org/jira/browse/HBASE-7233
> Project: HBase
> Issue Type: Bug
> Reporter: stack
> Assignee: stack
> Priority: Blocker
> Attachments: 7233.txt, 7233-v2.txt
>
>
> Undo KeyValue being a Writable.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
