You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Ralph Goers (JIRA)" <ji...@apache.org> on 2017/10/29 21:34:03 UTC
[jira] [Comment Edited] (HADOOP-12956) Inevitable Log4j2 migration
via slf4j
[ https://issues.apache.org/jira/browse/HADOOP-12956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16224215#comment-16224215 ]
Ralph Goers edited comment on HADOOP-12956 at 10/29/17 9:33 PM:
----------------------------------------------------------------
I have to question why you would move to SLF4J as the API when you can accomplish the same thing using the Log4j 2 API and the Log4j 2 API provides many more features than SLF4J.
was (Author: ralph.goers@dslextreme.com):
I have to question why you would move to SLF4J as the API when you can accomplish the same thing using the Log4j 2 API.
> Inevitable Log4j2 migration via slf4j
> -------------------------------------
>
> Key: HADOOP-12956
> URL: https://issues.apache.org/jira/browse/HADOOP-12956
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Gopal V
> Assignee: Haohui Mai
>
> {{5 August 2015 --The Apache Logging Services™ Project Management Committee (PMC) has announced that the Log4j™ 1.x logging framework has reached its end of life (EOL) and is no longer officially supported.}}
> https://blogs.apache.org/foundation/entry/apache_logging_services_project_announces
> A whole framework log4j2 upgrade has to be synchronized, partly for improved performance brought about by log4j2.
> https://logging.apache.org/log4j/2.x/manual/async.html#Performance
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org