Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <23540813.1193396091097.JavaMail.jira@brutus>
Date: Fri, 26 Oct 2007 03:54:51 -0700 (PDT)
From: "Enis Soztutar (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Commented: (HADOOP-1733) LocalJobRunner uses old-style
 job/tip ids
In-Reply-To: <33229255.1187447070926.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-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537922 ] 

Enis Soztutar commented on HADOOP-1733:
---------------------------------------

bq. We should never parse job ids, but only require them to be sufficiently unique.
Actually we may sometimes need to parse the {job|tip|task}ids where we do not have the relevant context to do the mappings such as taskid -> jobid, etc. An illustrating case is in the patch for HADOOP-53, where we need to parse the taskid to obtain the job and tip id in TaskTracker$Child. 

I guess this issue should be fixed as a part of Hadoop-544, so that parsing should never be done by the user, but the framework itself. 

> LocalJobRunner uses old-style job/tip ids
> -----------------------------------------
>
>                 Key: HADOOP-1733
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1733
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.14.0
>            Reporter: Arun C Murthy
>            Assignee: Arun C Murthy
>             Fix For: 0.16.0
>
>
> We should rework LocalJobRunner to use the new style job/tip ids (post HADOOP-1473).
> Is this a *blocker*? This isn't a functionality bug, yet ...

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