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

Posted to issues@bigtop.apache.org by "Masatake Iwasaki (Jira)" <ji...@apache.org> on 2021/12/16 01:31:00 UTC

[jira] [Commented] (BIGTOP-3615) Upgrade log4j2 of Hive 3.1.2 to 2.16.0

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

Masatake Iwasaki commented on BIGTOP-3615:
------------------------------------------

I updated the issue title based on the discussion of PR #841. We should use log4j 2.16.0 now.

> Upgrade log4j2 of Hive 3.1.2 to 2.16.0
> --------------------------------------
>
>                 Key: BIGTOP-3615
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-3615
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: hive
>    Affects Versions: 3.0.0
>            Reporter: Masatake Iwasaki
>            Assignee: Masatake Iwasaki
>            Priority: Major
>             Fix For: 3.1.0, 3.0.1
>
>          Time Spent: 2h 10m
>  Remaining Estimate: 0h
>
> HIVE-25795 upgraded log4j2 to 2.15.0 for CVE-2021-44228. We need the patch of HIVE-22278 too for Hive 3.1.2.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)