Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <26452228.1193898050607.JavaMail.jira@brutus>
Date: Wed, 31 Oct 2007 23:20:50 -0700 (PDT)
From: "stack (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Updated: (HADOOP-2083) [hbase] TestTableIndex failed in
 patch build #970 and #956
In-Reply-To: <23558812.1192840130815.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

    Fix Version/s: 0.16.0
           Status: Patch Available  (was: Open)

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