[
https://issues.apache.org/jira/browse/MAPREDUCE-4629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450787#comment-13450787
]
Hudson commented on MAPREDUCE-4629:
-----------------------------------
Integrated in Hadoop-Hdfs-trunk-Commit #2769 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/2769/])
MAPREDUCE-4629. Remove JobHistory.DEBUG_MODE (Karthik Kambatla via bobby)
(Revision 1382088)
Result = SUCCESS
bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1382088
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/main/java/org/apache/hadoop/mapreduce/v2/jobhistory/JHAdminConfig.java
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/main/java/org/apache/hadoop/mapreduce/v2/jobhistory/JobHistoryUtils.java
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs/src/main/java/org/apache/hadoop/mapreduce/v2/hs/HistoryFileManager.java
> 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
> Fix For: 1.2.0, 2.2.0-alpha
>
> Attachments: branch1-mr-4629.patch, MR-4629.patch, MR-4629.patch.v1,
> trunk-mr-6429.patch, 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
