[
https://issues.apache.org/jira/browse/PIG-5426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rohini Palaniswamy updated PIG-5426:
------------------------------------
Fix Version/s: 0.19.0
(was: 0.18.0)
Running into issues. As 0.18 is delayed long enough, migrating to reload4j in
that release as part of PIG-5434. Will migrate to log4j2.x in the next release.
> Migrate to log4j2.x
> -------------------
>
> Key: PIG-5426
> URL: https://issues.apache.org/jira/browse/PIG-5426
> Project: Pig
> Issue Type: Improvement
> Reporter: Rohini Palaniswamy
> Assignee: Rohini Palaniswamy
> Priority: Major
> Fix For: 0.19.0
>
>
> Hadoop (HADOOP-18088) decided to migrate to reload4j to address log4j1.x
> vulnerabilities. I did the work of migrating Oozie server and client to
> log4j2.x while launched hadoop jobs will still use 1.x till hadoop migrates.
> So think it should be easy to do that for pig client as well. If it does not
> work as expected, will just go with the easy switch to reload4j.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
