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

Hudson commented on HBASE-10323:
--------------------------------

FAILURE: Integrated in HBase-0.94-on-Hadoop-2 #65 (See 
[https://builds.apache.org/job/HBase-0.94-on-Hadoop-2/65/])
HBASE-10921 Port HBASE-10323 'Auto detect data block encoding in 
HFileOutputFormat' to 0.94 (Kashif) (tedyu: rev 1586701)
* 
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/mapreduce/HFileOutputFormat.java
* 
/hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/mapreduce/TestHFileOutputFormat.java


> Auto detect data block encoding in HFileOutputFormat
> ----------------------------------------------------
>
>                 Key: HBASE-10323
>                 URL: https://issues.apache.org/jira/browse/HBASE-10323
>             Project: HBase
>          Issue Type: Improvement
>          Components: mapreduce
>            Reporter: Ishan Chhabra
>            Assignee: Ishan Chhabra
>             Fix For: 0.98.0, 0.99.0
>
>         Attachments: HBASE_10323-0.94.15-v1.patch, 
> HBASE_10323-0.94.15-v2.patch, HBASE_10323-0.94.15-v3.patch, 
> HBASE_10323-0.94.15-v4.patch, HBASE_10323-0.94.15-v5.patch, 
> HBASE_10323-trunk-v1.patch, HBASE_10323-trunk-v2.patch, 
> HBASE_10323-trunk-v3.patch, HBASE_10323-trunk-v4.patch
>
>
> Currently, one has to specify the data block encoding of the table explicitly 
> using the config parameter 
> "hbase.mapreduce.hfileoutputformat.datablock.encoding" when doing a bulkload 
> load. This option is easily missed, not documented and also works differently 
> than compression, block size and bloom filter type, which are auto detected. 
> The solution would be to add support to auto detect datablock encoding 
> similar to other parameters. 
> The current patch does the following:
> 1. Automatically detects datablock encoding in HFileOutputFormat.
> 2. Keeps the legacy option of manually specifying the datablock encoding
> around as a method to override auto detections.
> 3. Moves string conf parsing to the start of the program so that it fails
> fast during starting up instead of failing during record writes. It also
> makes the internals of the program type safe.
> 4. Adds missing doc strings and unit tests for code serializing and
> deserializing config paramerters for bloom filer type, block size and
> datablock encoding.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to