You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@pig.apache.org by "Anoop Sam John (Jira)" <ji...@apache.org> on 2022/09/12 04:56:00 UTC

[jira] [Commented] (PIG-5426) Migrate to log4j2.x

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

Anoop Sam John commented on PIG-5426:
-------------------------------------

Planning to provide a patch [~rohini].  Thanks

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