hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-12883) Support block encoding based on knowing set of column qualifiers up front
Date Tue, 20 Jan 2015 18:18:35 GMT

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

Andrew Purtell commented on HBASE-12883:

Block encoders get a HFileContext reference. The reader could retrieve such a dictionary from
an HFile meta entry and pass it through HFileContext. Up in Store we create HFileContexts
with a builder for passing down HFile level configuration. There we could look for a schema
attribute that holds a supplied dictionary and pass it through. Phoenix could set up this
dictionary of column qualifiers in the column schema. The HFile writer could store the dictionary
into an HFile meta entry when writing out the file. If the application messes up they have
an unreadable HFile, that can be documented as the contract of this option. 

> Support block encoding based on knowing set of column qualifiers up front
> -------------------------------------------------------------------------
>                 Key: HBASE-12883
>                 URL: https://issues.apache.org/jira/browse/HBASE-12883
>             Project: HBase
>          Issue Type: Bug
>            Reporter: James Taylor
>              Labels: Phoenix
> Phoenix knows up front the set of column qualifiers a row will have. We could likely
get some good compression with little CPU based on this by having a block encoding scheme
that leverages this information. It could be made non-Phoenix specific by identifying the
set of column qualifiers through meta data to the block encoder.

This message was sent by Atlassian JIRA

View raw message