You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by "Sebastian Nagel (JIRA)" <ji...@apache.org> on 2016/04/29 18:15:13 UTC
[jira] [Assigned] (NUTCH-2256) Inconsistent log level practice
[ https://issues.apache.org/jira/browse/NUTCH-2256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sebastian Nagel reassigned NUTCH-2256:
--------------------------------------
Assignee: Sebastian Nagel
> Inconsistent log level practice
> -------------------------------
>
> Key: NUTCH-2256
> URL: https://issues.apache.org/jira/browse/NUTCH-2256
> Project: Nutch
> Issue Type: Bug
> Components: fetcher
> Affects Versions: 2.2, 2.3, 1.11, 2.3.1
> Reporter: songwanging
> Assignee: Sebastian Nagel
> Priority: Minor
> Fix For: 2.4, 1.12, 2.3.2
>
>
> In method "run()" of class: apache-nutch 2.3.1\src\java\org\apache\nutch\fetcher\FetcherReducer.java
> The log level is not correct, after checking "LOG.isDebugEnabled()", we should use "LOG.debug(msg, e);", while now we use " LOG.info(msg, e);". In this case, the log level is inconsistent and developers may lose debug messages because of this.
> The related source code is as follows:
> if (LOG.isDebugEnabled()) {
> LOG.info("Crawl delay for queue: " + fit.queueID
> + " is set to " + fiq.crawlDelay
> + " as per robots.txt. url: " + fit.url);
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)