Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <283658264.1234367819747.JavaMail.jira@brutus>
Date: Wed, 11 Feb 2009 07:56:59 -0800 (PST)
From: "Runping Qi (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-5203) TT's version build is too
 restrictive
In-Reply-To: <1310925896.1234200899626.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-5203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672661#action_12672661 ] 

Runping Qi commented on HADOOP-5203:
------------------------------------


You may be able to do a compatible build for 32bits and 64bits version.
How about for the environments with different OS?Different architectures?
We happen to be in an environment hadoop has to be built for different kinds of environments on different machines.
 

> TT's version build is too restrictive
> -------------------------------------
>
>                 Key: HADOOP-5203
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5203
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.19.0
>            Reporter: Runping Qi
>
> At start time, TT checks whether its version is compatible with JT.
> The condition is too restrictive. 
> It will shut down itself if one of the following conditions fail:
> * the version numbers must match
> * the revision numbers must match
> * the user ids who build the jar must match
> * the build times must match
> I think it should check the major part of the version numbers only (thus any version like 0.19.xxxx should be compatible).

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