[
https://issues.apache.org/jira/browse/HBASE-7233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13527331#comment-13527331
]
Matt Corgan commented on HBASE-7233:
------------------------------------
I wouldn't mind dropping the "DataBlock" prefix as it gets a little unwieldy in
places. It's a confusing right now that there is a DataBlockEncoder which
arranges bytes and an HFileDataBlockEncoder that sets up and triggers the
DataBlockEncoder. There is also a NoOpDataBlockEncoder which should really be
called NoOpHFileDataBlockEncoder. Could do:
DataBlockEncoding -> Encoding
DataBlockEncoder -> Encoder
HFileDataBlockEncoder -> HFileEncoder
NoOpDataBlockEncoder -> NoOpHFileEncoder
HFileBlockEncodingContext -> HFileEncodingContext
Though the HFileEncoders are not really encoders at heart - they're just
setting up the environment for the actual encoders. It's more like an
HFileBlockConverter.
> 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
