hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-2083) [hbase] TestTableIndex failed in patch build #970 and #956
Date Thu, 01 Nov 2007 07:50:50 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539297

Hadoop QA commented on HADOOP-2083:

+1 overall.  Here are the results of testing the latest attachment 
against trunk revision r590875.

    @author +1.  The patch does not contain any @author tags.

    javadoc +1.  The javadoc tool did not generate any warning messages.

    javac +1.  The applied patch does not generate any new compiler warnings.

    findbugs +1.  The patch does not introduce any new Findbugs warnings.

    core tests +1.  The patch passed core unit tests.

    contrib tests +1.  The patch passed contrib unit tests.

Test results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1047/testReport/
Findbugs warnings: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1047/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1047/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1047/console

This message is automatically generated.

> [hbase] TestTableIndex failed in patch build #970 and #956
> ----------------------------------------------------------
>                 Key: HADOOP-2083
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2083
>             Project: Hadoop
>          Issue Type: Bug
>          Components: contrib/hbase
>            Reporter: stack
>             Fix For: 0.16.0
>         Attachments: mrt-v2.patch, mrt.patch
> TestTableIndex failed in two nightly builds.
> The fancy trick of passing around a complete configuration with per column indexing specification
extensions inside in a Configuration value is biting us.  The interpolation code has an upper
bound of 20 interpolations.
> Looking at seeing if I can run the interpolations before inserting the config.  else
need to move to have Configuration.substituteVars made protected so can fix ... or do config.
for this job in another way.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message