[
https://issues.apache.org/jira/browse/HBASE-5521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13222608#comment-13222608
]
Phabricator commented on HBASE-5521:
------------------------------------
tedyu has commented on the revision "HBASE-5521 [jira] Move
compression/decompression to an encoder specific encoding context".
Still going over the new Context interfaces.
INLINE COMMENTS
src/main/java/org/apache/hadoop/hbase/io/encoding/HFileBlockEncodingContext.java:51
I don't find where this method is used.
src/main/java/org/apache/hadoop/hbase/io/hfile/HFileBlock.java:690 There is
nothing to be done between preparation and post processing ?
src/main/java/org/apache/hadoop/hbase/io/hfile/HFileBlock.java:693
nonDataBlockEncodingCtx should be used here, I assume.
REVISION DETAIL
https://reviews.facebook.net/D2097
> Move compression/decompression to an encoder specific encoding context
> ----------------------------------------------------------------------
>
> Key: HBASE-5521
> URL: https://issues.apache.org/jira/browse/HBASE-5521
> Project: HBase
> Issue Type: Improvement
> Reporter: He Yongqiang
> Assignee: He Yongqiang
> Attachments: HBASE-5521.1.patch, HBASE-5521.D2097.1.patch
>
>
> As part of working on HBASE-5313, we want to add a new columnar
> encoder/decoder. It makes sense to move compression to be part of
> encoder/decoder:
> 1) a scanner for a columnar encoded block can do lazy decompression to a
> specific part of a key value object
> 2) avoid an extra bytes copy from encoder to hblock-writer.
> If there is no encoder specified for a writer, the HBlock.Writer will use a
> default compression-context to do something very similar to today's code.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
