hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7233) Serializing KeyValues
Date Sat, 08 Dec 2012 00:51:21 GMT

    [ https://issues.apache.org/jira/browse/HBASE-7233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526937#comment-13526937
] 

stack commented on HBASE-7233:
------------------------------

bq. Will clients ever want a value in the mvccVersion?

No.  MVCC is server internals.

bq. 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. 

Streaming Interface sounds good.  Should we call these new base classes Encoder, Encoding,
Context, etc..... i.e. drop the DataBlock prefix.  Hopefully DataBlockEncoder could inherit
Encoder.
                
> 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

Mime
View raw message