You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-issues@hadoop.apache.org by "Chris Douglas (JIRA)" <ji...@apache.org> on 2009/12/23 03:11:30 UTC

[jira] Updated: (MAPREDUCE-1236) added LOG.isdebugenabled for LOG.debug() as noted in MAPREDUCE-1026

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

Chris Douglas updated MAPREDUCE-1236:
-------------------------------------

    Assignee: Boris Shkolnik
      Status: Open  (was: Patch Available)

Unfortunately, the patch no longer applies.

The guarding of log statements is a little excessive in the most recent patch. Unless it's frequent and/or involves many conversions of non-String types, it's OK to leave it unguarded.

> added LOG.isdebugenabled for LOG.debug() as noted in MAPREDUCE-1026
> -------------------------------------------------------------------
>
>                 Key: MAPREDUCE-1236
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1236
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>            Reporter: Boris Shkolnik
>            Assignee: Boris Shkolnik
>            Priority: Minor
>         Attachments: MAPREDUCE-1236.patch
>
>
> in /MAPREDUCE-1026 we introduces few LOG.debug() not constrained by LOG.isdebugenabed() .
> Fixing that.

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