[
https://issues.apache.org/jira/browse/HADOOP-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun C Murthy resolved HADOOP-1733.
-----------------------------------
Resolution: Won't Fix
HADOOP-544 will make this moot... either way, as Doug notes:
{quote}
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.
{quote}
> 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.
