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

Peter Bacsko edited comment on OOZIE-3136 at 10/10/18 6:56 AM:
---------------------------------------------------------------

So looks like the plan is
 # Add log4j-api12 dependency
 # Remove log4j-specific calls from XLogService, add new log4j2 setup code
 # Rewrite OozieRollingPolicy or rewrite streaming code
 # Adapt the remaining classes to log4j2:
 ** TestXLogService.java
 ** TestXLogStreamingService.java
 ** XLogUtil.java
 ** LocalOozie.java
 ** TestSignalXCommand.java
 ** ... some other test classes
 # Remove log4j dependency
 # Test like crazy, especially streaming and backward compatibility

Anything I missed? I think we're fine with the YARN/sharelib side. So it's only 
oozie-core.

Can we give a possible ETA to the Bigtop guys? I assume it's at least 4-5 
weeks, perhaps more.


was (Author: pbacsko):
So looks like the plan is

# Add log4j-api12 dependency
# Remove log4j-specific calls from XLogService, add new log4j2 setup code
# Rewrite OozieRollingPolicy or rewrite streaming code
# Adapt the remaining classes to log4j2:
** TestXLogService.java
** TestXLogStreamingService.java
** XLogUtil.java
** LocalOozie.java
** TestSignalXCommand.java
** ... some other test classes
# Remove log4j dependency
# Test like crazy, especially streaming and backward compatibility

Anything I missed?

Can we give a possible ETA to the Bigtop guys? I assume it's at least 4-5 
weeks, perhaps more.


> 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)

Reply via email to