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] [Updated] (HDFS-6564) Use slf4j instead of common-logging in hdfs-client
Date Tue, 23 Jun 2015 02:27:01 GMT

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

Rakesh R updated HDFS-6564:
    Release Note: 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 will use slf4j framework. For more details about slf4j, please see: 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.slf4j.Logger LOG = org.slf4j.LoggerFactory.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