[
https://issues.apache.org/jira/browse/HBASE-7233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526071#comment-13526071
]
Matt Corgan commented on HBASE-7233:
------------------------------------
Will clients ever want a value in the mvccVersion? We can probably nullify
that when encoding for the client, so maybe the includesMemstoreTS parameter is
necessary?
In the replacement interface, we'll want to switch from encoding a ByteBuffer
of KeyValue format bytes to a streaming interface where Cells are given to the
encoder individually and a flush method is called when you want the encoded
byte[] spit out. We should probably split the Encoder, Decoder, and Seeker
interfaces as well.
> 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
> Fix For: 0.96.0
>
> 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
