hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-415) JobControl Job does always has an unassigned name
Date Thu, 25 Feb 2010 00:03:28 GMT

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

Allen Wittenauer commented on MAPREDUCE-415:
--------------------------------------------

It does in the sense that the patch appears to be very low risk, low key and is just sort
of sitting here.  I've marked it as patch available and so we'll see what happens from here.

> 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