hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7936) Undo prefix-tree module as dependency for mapreduce and for DataBlockEncoding
Date Fri, 01 Mar 2013 18:35:13 GMT

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

Ted Yu commented on HBASE-7936:

Two tests failed due to the removal of hbase-server's dependency on hbase-prefix-tree.
In TestHFileDataBlockEncoder:
    for (DataBlockEncoding diskAlgo : DataBlockEncoding.values()) {
Without the dependency, we get:
java.lang.IllegalArgumentException: java.lang.ClassNotFoundException: org.apache.hbase.codec.prefixtree.PrefixTreeCodec
	at org.apache.hadoop.hbase.io.encoding.DataBlockEncoding.createEncoder(DataBlockEncoding.java:189)
	at org.apache.hadoop.hbase.io.encoding.DataBlockEncoding.getEncoder(DataBlockEncoding.java:128)
	at org.apache.hadoop.hbase.io.hfile.HFileDataBlockEncoderImpl.<init>(HFileDataBlockEncoderImpl.java:80)
	at org.apache.hadoop.hbase.io.hfile.HFileDataBlockEncoderImpl.<init>(HFileDataBlockEncoderImpl.java:60)
	at org.apache.hadoop.hbase.io.hfile.TestHFileDataBlockEncoder.getAllConfigurations(TestHFileDataBlockEncoder.java:178)
> Undo prefix-tree module as dependency for mapreduce and for DataBlockEncoding
> -----------------------------------------------------------------------------
>                 Key: HBASE-7936
>                 URL: https://issues.apache.org/jira/browse/HBASE-7936
>             Project: HBase
>          Issue Type: Task
>            Reporter: stack
>            Assignee: Ted Yu
>             Fix For: 0.95.0, 0.98.0
>         Attachments: 7936-trunk.addendum, 7936.txt
> Fix DBE so it does lazy loading rather than hard loading of everything mentioned.
> Client depends on prefix-tree module since HBASE-7188 and mapreduce will after hbase-7934

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

View raw message