hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Joseph Evans (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-4629) Remove JobHistory.DEBUG_MODE
Date Fri, 07 Sep 2012 16:14:08 GMT

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

Robert Joseph Evans updated MAPREDUCE-4629:

    Attachment: trunk-mr-6429.patch

Uploading the trunk patch again, unchanged to Jenkins can run the precommit build on it.

The changes look good to me.  Assuming Jenkins comes back OK I am a +1 on the changes for
trunk.  Assuming my running the unit tests on branhc-1 come back OK I am +1 for that as well.
> Remove JobHistory.DEBUG_MODE
> ----------------------------
>                 Key: MAPREDUCE-4629
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4629
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 1.0.3, 2.0.0-alpha
>            Reporter: Karthik Kambatla
>            Assignee: Karthik Kambatla
>         Attachments: branch1-mr-4629.patch, MR-4629.patch, MR-4629.patch.v1, trunk-mr-6429.patch,
> Remove JobHistory.DEBUG_MODE for the following reasons:
> 1. No one seems to be using it - the config parameter corresponding to enabling it does
not even exist in mapred-default.xml
> 2. The logging being done in DEBUG_MODE needs to move to LOG.debug() and LOG.trace()
> 3. Buggy handling of helper methods in DEBUG_MODE; e.g. directoryTime() and timestampDirectoryComponent().

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message