You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Jonathan Hsieh (JIRA)" <ji...@apache.org> on 2013/09/26 19:38:03 UTC
[jira] [Resolved] (HBASE-9661) Consistent log severity level guards
and statements
[ https://issues.apache.org/jira/browse/HBASE-9661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Hsieh resolved HBASE-9661.
-----------------------------------
Resolution: Fixed
> Consistent log severity level guards and statements
> ----------------------------------------------------
>
> Key: HBASE-9661
> URL: https://issues.apache.org/jira/browse/HBASE-9661
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 0.95.2
> Reporter: Jackie Chang
> Assignee: Jackie Chang
> Priority: Minor
> Fix For: 0.98.0, 0.96.0
>
> Attachments: HBASE-9661.patch
>
>
> A log statement should be guarded by its matching severity level. A log statement like
> if (LOG.isTraceEnabled()) {
> LOG.debug(identifier + " opening connection to ZooKeeper ensemble=" + ensemble);
> doesn't make much sense because the log message is only printed out when TRACE-level is enabled. This inconsistency was possibly introduced when developers demoted the original log statement from DEBUG but forgot to change its corresponding log severity level.
--
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