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

Posted to dev@kafka.apache.org by "Jun Rao (JIRA)" <ji...@apache.org> on 2013/03/05 18:14:14 UTC

[jira] [Resolved] (KAFKA-105) switch to using slf4j

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

Jun Rao resolved KAFKA-105.
---------------------------

    Resolution: Won't Fix

Since we now have the Logger class, which gives us most of the benefits of slf4j api, we can resolve this jira for now.
                
> switch to using slf4j
> ---------------------
>
>                 Key: KAFKA-105
>                 URL: https://issues.apache.org/jira/browse/KAFKA-105
>             Project: Kafka
>          Issue Type: Improvement
>          Components: core
>            Reporter: Chris Burroughs
>            Assignee: Chris Burroughs
>
> Breaking out discussion from KAFKA-96.  
> slf4j has a cleaner (and faster) way of not logging: http://www.slf4j.org/faq.html#logging_performance that avoid both the redundant if's and string con-catting.  slf4j is just an api, we would still use log4j for the actual logging in the standalone server.  This also makes it easier on downstream projects who are not using log4j.  The downside is that java logging is notoriously complicated, and now we would have two logging frameworks that can break.
> Discussion from other projects; ZOOKEEPER-850, SOLR-560 HBASE-2608, CASSANDRA-625, THRIFT-558

--
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