hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-1906) JobConf should warn about the existance of obsolete mapred-default.xml.
Date Fri, 05 Oct 2007 18:56:50 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532750

Hadoop QA commented on HADOOP-1906:

-1 overall.  Here are the results of testing the latest attachment 
against trunk revision r582165.

    @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/893/testReport/
Findbugs warnings: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/893/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/893/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/893/console

This message is automatically generated.

> JobConf should warn about the existance of obsolete mapred-default.xml.
> -----------------------------------------------------------------------
>                 Key: HADOOP-1906
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1906
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: conf
>            Reporter: Owen O'Malley
>            Assignee: Arun C Murthy
>             Fix For: 0.15.0
>         Attachments: HADOOP-1906_1_20071005.patch
> Since the mapred-default.xml is ignored after HADOOP-785, we should generate a warning
when it is present. Otherwise users forget to move the values to hadoop-site.xml and get 
confused when things don't work right.

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

View raw message