hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rakesh R (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-6564) Use slf4j instead of common-logging in hdfs-client
Date Fri, 19 Jun 2015 05:07:01 GMT

    [ https://issues.apache.org/jira/browse/HDFS-6564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14593015#comment-14593015

Rakesh R commented on HDFS-6564:

We have an example mentioned in the previous note.
org.slf4j.Logger LOG = org.slf4j.LoggerFactory.getLogger(org.apache.hadoop.hdfs.protocol.CachePoolInfo.class);
I think I can include link of slf4j manual in the note like below. Does this sound good to
you ?
Users may need special attention for this change while upgrading to this version. Previously
hdfs client was using commons-logging as the logging framework. With this change it uses slf4j
framework. For more details: http://www.slf4j.org/manual.html. Also, org.apache.hadoop.hdfs.protocol.CachePoolInfo#LOG
public static member variable has been removed as it is not used anywhere. Users need to correct
their code if any one has a reference to this variable. One can retrieve the named logger
via the logging framework of their choice directly like, org.apache.commons.logging.Log LOG
= org.apache.commons.logging.LogFactory.getLogger(org.apache.hadoop.hdfs.protocol.CachePoolInfo.class);

> Use slf4j instead of common-logging in hdfs-client
> --------------------------------------------------
>                 Key: HDFS-6564
>                 URL: https://issues.apache.org/jira/browse/HDFS-6564
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Haohui Mai
>            Assignee: Rakesh R
>         Attachments: HDFS-6564-01.patch, HDFS-6564-02.patch, HDFS-6564-03.patch
> hdfs-client should depends on slf4j instead of common-logging.

This message was sent by Atlassian JIRA

View raw message