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 "Ted Dunning (JIRA)" <ji...@apache.org> on 2007/09/30 04:50:51 UTC
[jira] Created: (HADOOP-1971) Constructing a JobConf without a
class leads to a very misleading error message.
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: Bug
Components: mapred
Affects Versions: 0.13.1
Environment: Centos, java 1.5
Reporter: Ted Dunning
Priority: Minor
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.
[jira] Updated: (HADOOP-1971) Constructing a JobConf without a
class leads to a very misleading error message.
Posted by "Enis Soztutar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Enis Soztutar updated HADOOP-1971:
----------------------------------
Attachment: notSetJarError_v1.patch
This simple patch adds a log warning complaining about not set jar file.
> 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.
[jira] Updated: (HADOOP-1971) Constructing a JobConf without a
class leads to a very misleading error message.
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Doug Cutting updated HADOOP-1971:
---------------------------------
Attachment: HADOOP-1971.patch
I think a warning is enough. There are cases where this may not be an error (e.g., if someone has installed their mapred classes on the cluster before startup) so the warning may sometimes be spurious, but those cases should be rare.
I changed the warning message to specifically complain about the root cause (no job jar specified) and point to potential solutions.
> 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.15.0
>
> Attachments: HADOOP-1971.patch, 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.
[jira] Commented: (HADOOP-1971) Constructing a JobConf without a
class leads to a very misleading error message.
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532132 ]
Hadoop QA commented on HADOOP-1971:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12366997/notSetJarError_v1.patch
against trunk revision r581492.
@author +1. The patch does not contain any @author tags.
javadoc +1. The javadoc tool did not generate any warning messages.
javac +1. The applied patch does not generate any new compiler warnings.
findbugs +1. The patch does not introduce any new Findbugs warnings.
core tests +1. The patch passed core unit tests.
contrib tests -1. The patch failed contrib unit tests.
Test results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/874/testReport/
Findbugs warnings: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/874/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/874/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/874/console
This message is automatically generated.
> 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.
[jira] Updated: (HADOOP-1971) Constructing a JobConf without a
class leads to a very misleading error message.
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Doug Cutting updated HADOOP-1971:
---------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
I just committed this.
> 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.15.0
>
> Attachments: HADOOP-1971.patch, 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.
[jira] Updated: (HADOOP-1971) Constructing a JobConf without a
class leads to a very misleading error message.
Posted by "Enis Soztutar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Enis Soztutar updated HADOOP-1971:
----------------------------------
Status: Patch Available (was: Open)
> 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.
[jira] Assigned: (HADOOP-1971) Constructing a JobConf without a
class leads to a very misleading error message.
Posted by "Enis Soztutar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Enis Soztutar reassigned HADOOP-1971:
-------------------------------------
Assignee: Enis Soztutar
> 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: Bug
> Components: mapred
> Affects Versions: 0.13.1
> Environment: Centos, java 1.5
> Reporter: Ted Dunning
> Assignee: Enis Soztutar
> Priority: Minor
>
> 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.
[jira] Updated: (HADOOP-1971) Constructing a JobConf without a
class leads to a very misleading error message.
Posted by "Enis Soztutar (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (HADOOP-1971) Constructing a JobConf without a
class leads to a very misleading error message.
Posted by "Owen O'Malley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Owen O'Malley updated HADOOP-1971:
----------------------------------
Fix Version/s: (was: 0.14.2)
0.15.0
This isn't a bug and so should not go into 14.2. I can see the motivation for the warning, but not all jobs need a jar file. We should probably move the examples to be more explicit and do:
{code}
JobConf conf = new JobConf();
conf.setJarByClass(MyClass.class);
{code}
so it will be more obvious when you drop it out what is likely to happen. *smile*
> 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.15.0
>
> 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.
[jira] Commented: (HADOOP-1971) Constructing a JobConf without a
class leads to a very misleading error message.
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532856 ]
Hudson commented on HADOOP-1971:
--------------------------------
Integrated in Hadoop-Nightly #263 (See [http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Nightly/263/])
> 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.15.0
>
> Attachments: HADOOP-1971.patch, 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.