[
https://issues.apache.org/jira/browse/HBASE-7233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13511233#comment-13511233
]
stack commented on HBASE-7233:
------------------------------
bq. I like the idea of KeyValue encoder.
It'd write <length><bytearray><length><bytearray> and the byte array would be
the backing array of a KV? The format version would be in the pb preamble.
Client would volunteer what it could digest. We'd package the kv
appropriately... version1 if that was what they asked for. If they asked for
version2, they'd get Andrew's tags if any specified?
A step above this would be a datablock encoder for sending lots of KVs in a
compact form.
bq. How controversial is this?
Rewriting all hfiles? Pretty controversial I'd say. Maybe you were talking
about how tricky versioning KV is?
Changed title of issue. Moved its original intent, removing Writable from KV
to HBASE-7289
> Serializing KeyValues
> ---------------------
>
> 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
