hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom White (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-415) JobControl Job does always has an unassigned name
Date Thu, 11 Mar 2010 00:19:27 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12843845#action_12843845
] 

Tom White commented on MAPREDUCE-415:
-------------------------------------

Since MAPREDUCE-368 went in this is no longer applicable to trunk. The new implementation
does not suffer from this problem, so I think we can close this issue.

> JobControl Job does always has an unassigned name
> -------------------------------------------------
>
>                 Key: MAPREDUCE-415
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-415
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: job submission
>    Affects Versions: 0.20.2, 0.21.0, 0.22.0
>            Reporter: Xavier Stevens
>            Priority: Minor
>         Attachments: hadoop-4777.patch
>
>
> When creating and adding org.apache.hadoop.mapred.jobcontrol.Job(s) they don't use the
names specified in their respective JobConf files.  Instead it's just hardcoded to "unassigned".

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


Mime
View raw message