Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 12 Jun 2014 03:52:01 +0000 (UTC)
From: "Andrew Purtell (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12720747.1402529204138.115087.1402545121738@arcas>
In-Reply-To: <JIRA.12720747.1402529204138@arcas>
References: <JIRA.12720747.1402529204138@arcas>
Subject: [jira] [Commented] (HBASE-11334) Migrate to SLF4J as logging
 interface
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Andrew Purtell commented on HBASE-11334:
----------------------------------------

Well we want to use log4j2's async back end, but they provide a bridge module for SLF4J so certainly the logger API we use in our code could be SLF4J, or commons logging -> SLF4J -> Log4J2

> Migrate to SLF4J as logging interface
> -------------------------------------
>
>                 Key: HBASE-11334
>                 URL: https://issues.apache.org/jira/browse/HBASE-11334
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: jay vyas
>
> Migrating to new log implementations is underway as in HBASE-10092. 
> Next step would be to abstract them so that the hadoop community can standardize on a logging layer that is easy for end users to tune.
> Simplest way to do this is use SLF4j APIs as the main interface and binding/ implementation details in the docs as necessary.


--
This message was sent by Atlassian JIRA
(v6.2#6252)