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 "Xavier Stevens (JIRA)" <ji...@apache.org> on 2008/12/05 00:04:44 UTC

[jira] Created: (HADOOP-4777) JobControl Job does always has an unassigned name

JobControl Job does always has an unassigned name
-------------------------------------------------

                 Key: HADOOP-4777
                 URL: https://issues.apache.org/jira/browse/HADOOP-4777
             Project: Hadoop Core
          Issue Type: Bug
          Components: mapred
    Affects Versions: 0.18.2
            Reporter: Xavier Stevens
            Priority: Minor


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.


[jira] Updated: (HADOOP-4777) JobControl Job does always has an unassigned name

Posted by "Xavier Stevens (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-4777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Xavier Stevens updated HADOOP-4777:
-----------------------------------

    Comment: was deleted

> JobControl Job does always has an unassigned name
> -------------------------------------------------
>
>                 Key: HADOOP-4777
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4777
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.18.2
>            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.


[jira] Updated: (HADOOP-4777) JobControl Job does always has an unassigned name

Posted by "Xavier Stevens (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-4777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Xavier Stevens updated HADOOP-4777:
-----------------------------------

    Attachment:     (was: hadoop-0.18-Job.patch)

> JobControl Job does always has an unassigned name
> -------------------------------------------------
>
>                 Key: HADOOP-4777
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4777
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.18.2
>            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.


[jira] Updated: (HADOOP-4777) JobControl Job does always has an unassigned name

Posted by "Xavier Stevens (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-4777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Xavier Stevens updated HADOOP-4777:
-----------------------------------

    Attachment: hadoop-4777.patch

Here's a patch which simply gets the job name from the passed in JobConf. 

> JobControl Job does always has an unassigned name
> -------------------------------------------------
>
>                 Key: HADOOP-4777
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4777
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.18.2
>            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.


[jira] Updated: (HADOOP-4777) JobControl Job does always has an unassigned name

Posted by "Xavier Stevens (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-4777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Xavier Stevens updated HADOOP-4777:
-----------------------------------

    Attachment: hadoop-0.18-Job.patch

Here's a patch which simply gets the job name from the passed in JobConf.

> JobControl Job does always has an unassigned name
> -------------------------------------------------
>
>                 Key: HADOOP-4777
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4777
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.18.2
>            Reporter: Xavier Stevens
>            Priority: Minor
>         Attachments: hadoop-0.18-Job.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.