hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gregory Chanan (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-5346) Fix testColumnFamilyCompression and test_TIMERANGE in TestHFileOutputFormat
Date Thu, 16 Feb 2012 00:41:00 GMT

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

Gregory Chanan commented on HBASE-5346:


Any comment on my previous message?  It looks like this can be committed, but my reading of
the results could be wrong.
>  Fix testColumnFamilyCompression and test_TIMERANGE in TestHFileOutputFormat
> ----------------------------------------------------------------------------
>                 Key: HBASE-5346
>                 URL: https://issues.apache.org/jira/browse/HBASE-5346
>             Project: HBase
>          Issue Type: Sub-task
>          Components: mapreduce, test
>    Affects Versions: 0.90.4, 0.92.0
>            Reporter: Gregory Chanan
>            Assignee: Gregory Chanan
>         Attachments: HBASE-5346-v0.patch
> Running
> mvn -Dhadoop.profile=23 test -P localTests -Dtest=org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat
> yields this on 0.92 (for testColumnFamilyCompression and test_TIMERANGE):
> Failed tests: testColumnFamilyCompression(org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat):
HFile for column family info-A not found
> Tests in error: 
> test_TIMERANGE(org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat): /home/gchanan/workspace/apache92/target/test-data/276cbd0c-c771-4f81-9ba8-c464c9dd7486/test_TIMERANGE_present/_temporary/0/_temporary/_attempt_200707121733_0001_m_000000_0
(Is a directory)
> The problem is that these tests make incorrect assumptions about the output of mapreduce
jobs.  Prior to 0.23, temporary data was in, for example:
> ./_temporary/_attempt__0000_r_000000_0/b/1979617994050536795
> Now that has changed.  The correct way to get that path is based on getDefaultWorkFile.
> Also, the data is not moved into the outputPath until both the Task and Job are committed.

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


View raw message