You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "stack (JIRA)" <ji...@apache.org> on 2007/10/31 23:22:50 UTC

[jira] Updated: (HADOOP-2083) [hbase] TestTableIndex failed in patch build #970 and #956

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

stack updated HADOOP-2083:
--------------------------

    Attachment: mrt.patch

Find the parent region BEFORE we start loading the table with content.  This way I'm sure to have the correct parent needed later when making assertions and trying to find names of daughter regions.

> [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
>         Attachments: 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.