[
https://issues.apache.org/jira/browse/HBASE-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12873942#action_12873942
]
Lars Francke commented on HBASE-2608:
-------------------------------------
Avro and Thrift pull in SLF4J last I looked but I'll soon be able to get back
to some work on HBase (Maven of course, you're responsible for the internal
technical stuff :) ).
Thanks for the hint about the UI log level servlet; with a little help I was
able to find that in hadoop-common and it looks like it'd be easy to write our
own implementation of that class. But that's only necessary if we switch from
log4j to logback. These changes shouldn't be necessary when we "just" use
SLF4J. Perhaps we should raise this issue with Hadoop as well, see what they
want to do.
Priority: No
Nice to have: Yes
It'd be just nice to ditch these old tools. Someone's got to start ;-) (And
you'd have the opportunity to build up new knowledge! But it really isn't that
different)
> Switch to SLF4J
> ---------------
>
> Key: HBASE-2608
> URL: https://issues.apache.org/jira/browse/HBASE-2608
> Project: 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.
