hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-2083) [hbase] TestTableIndex failed in patch build #970 and #956
Date Wed, 31 Oct 2007 22:20:50 GMT

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

stack commented on HADOOP-2083:

#1041 failure in TestTableIndex was because an assertion that the table was multiregion failed.
 Was also cause of the other test failure, in TestTableMapReduce in patch build #1040.  The
code that finds the parent is flawed in that it doesn't allow that the parent region may have
already split at time we go to provoke split.  Same issue in #1038 failure.

> [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
> 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