[
https://issues.apache.org/jira/browse/OOZIE-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16642946#comment-16642946
]
Julia Kinga Marton edited comment on OOZIE-3136 at 10/9/18 8:25 AM:
--------------------------------------------------------------------
I totally agree that at some point we will need to make a complete migration.
This is cleaner path and only using this approach we will be able to use the
new functionalities introduced by Log4j2.
Since there is no way to keep compatibility, I would change the .property based
configuration to the xml configuration.
I was also thinking about waiting LOG4J2-63 but I did not see any progress
since last year.
was (Author: kmarton):
I totally agree that at some point we will need to make a complete migration.
This is cleaner and only using this approach will be able to use the new
functionalities introduced by Log4j2.
Since there is no way to keep compatibility, I would change the .property based
configuration to the xml configuration.
I was also thinking about waiting LOG4J2-63 but I did not see any progress
since last year.
> Upgrade from Log4j 1.x to 2.x
> -----------------------------
>
> Key: OOZIE-3136
> URL: https://issues.apache.org/jira/browse/OOZIE-3136
> Project: Oozie
> Issue Type: Sub-task
> Reporter: Attila Sasvari
> Assignee: Julia Kinga Marton
> Priority: Major
>
> {{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
> We should upgrade from Log4j 1.x to 2.x . Perhaps we could use slf4j .
> Related tickets: MAPREDUCE-6983, HADOOP-12956, OOZIE-3135
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
