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 "Enis Soztutar (JIRA)" <ji...@apache.org> on 2007/10/03 14:24:50 UTC

[jira] Updated: (HADOOP-1971) Constructing a JobConf without a class leads to a very misleading error message.

     [ https://issues.apache.org/jira/browse/HADOOP-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Enis Soztutar updated HADOOP-1971:
----------------------------------

        Fix Version/s: 0.14.2
           Issue Type: Improvement  (was: Bug)
    Affects Version/s:     (was: 0.13.1)
                       0.14.2

changing version to 0.14.2. 

> Constructing a JobConf without a class leads to a very misleading error message.
> --------------------------------------------------------------------------------
>
>                 Key: HADOOP-1971
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1971
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: mapred
>    Affects Versions: 0.14.2
>         Environment: Centos, java 1.5
>            Reporter: Ted Dunning
>            Assignee: Enis Soztutar
>            Priority: Minor
>             Fix For: 0.14.2
>
>         Attachments: notSetJarError_v1.patch
>
>
> If this line from a typical map/reduce program
>         JobConf conf = new JobConf(Flatten.class);
> has the argument deleted then I get a message that the input format that I specify cannot be found.  That message leads a naive user on a rat chase.  I only corrected this by bisecting against a working program.

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