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

Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2010/05/24 17:03:25 UTC

[jira] Commented: (HBASE-2608) Switch to SLF4J

    [ https://issues.apache.org/jira/browse/HBASE-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12870627#action_12870627 ] 

stack commented on HBASE-2608:
------------------------------

We log against apache commons.  Isn't changing to use slf4j just a matter of a config. change?  (Or, rather it seems that apache commons logging will use log4j if its found in the classapath).

> Switch to SLF4J
> ---------------
>
>                 Key: HBASE-2608
>                 URL: https://issues.apache.org/jira/browse/HBASE-2608
>             Project: Hadoop HBase
>          Issue Type: Improvement
>            Reporter: Benoit Sigoure
>
> There are 2 compelling reasons to switch from log4j to slf4j:
> * HBase provides a client library that is going to be embedded in another application.  Using SLF4J lets the application chose whatever logging library it wants instead of imposing log4j.
> * When using SLF4J, we should use logback by default as it is basically a better, faster, stronger log4j.  Same author, new design / new code.  See http://logback.qos.ch/reasonsToSwitch.html

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