[
https://issues.apache.org/jira/browse/OOZIE-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16643002#comment-16643002
]
Andras Piros commented on OOZIE-3136:
-------------------------------------
[~pbacsko] [~asalamon74] [~kmarton] HADOOP-12596 seems really a good read, as
is HBASE-10092. It seems that we indeed need to go for the {{slf4j-log4j12}}
adapter based approach because:
# in Oozie 5.x, we need that old {{.properties}} based configuration remains
working, else we would break compatibility guidelines for a minor version. In
Oozie 6.0 we may consider moving to {{log4j2}} completely, thus breaking
backwards compatibility guarantees
# as there are many Oozie users that have custom {{.properties}} settings we
need those settings remain working in Oozie 5.x
# caveats of the same type you mentioned do exist on Oozie 5.0: if the user has
a fat JAR consisting also of {{log4j12}} classes that are versions incompatible
w/ the Oozie server / sharelib's version, we can see lots of
{{ClassNotFoundException}} instances, and other types of class loading errors,
as well as strange behavior like logging doesn't work silently at all. The
general recommendation has been to either avoid packing those classes inside
user JARs, or to use {{maven-shade-plugin}} to hide those
All in all, I'm for using adapter classes and maintain {{log4j12}}
configuration throughout Oozie 5.x. [~gezapeti] [~asasvari] what do you think?
> 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)
