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 "Doug Cutting (JIRA)" <ji...@apache.org> on 2007/10/25 19:59:50 UTC

[jira] Commented: (HADOOP-1733) LocalJobRunner uses old-style job/tip ids

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

Doug Cutting commented on HADOOP-1733:
--------------------------------------

I don't see a need for job ids to be identical between localrunner and jobtracker.  User code should not rely on the format of job ids.  Having them different helps enforce that!  We should never parse job ids, but only require them to be sufficiently unique.

So we should change the format of localrunner's job ids if they're not sufficiently unique.  I'm aware of no bugs resulting from localrunner job id clashes.  If any arise, then we might revisit this issue, otherwise I think we should resolve this as "won't fix".


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