[jira] [Resolved] (IMPALA-13049) Add dependency management for the log4j2 version

["Joe McDonnell (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IMPALA-13049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joe McDonnell resolved IMPALA-13049.
------------------------------------
    Fix Version/s: Impala 4.5.0
       Resolution: Fixed

> Add dependency management for the log4j2 version
> ------------------------------------------------
>
>                 Key: IMPALA-13049
>                 URL: https://issues.apache.org/jira/browse/IMPALA-13049
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Frontend, Infrastructure
>    Affects Versions: Impala 4.4.0
>            Reporter: Joe McDonnell
>            Assignee: Joe McDonnell
>            Priority: Critical
>             Fix For: Impala 4.5.0
>
>
> In some internal builds, we see cases where one dependency brings in one version of log4j2 and another brings in a different version on a different artifact. In particular, we have seen cases where Hive brings in log4j-api 2.17.1 while something else brings in log4j-core 2.18.0. This is a bad combination, because log4j-core 2.18.0 relies on the ServiceLoaderUtil class existing in log4j-api, but log4j-api 2.17.1 doesn't have it. This can result in class not found exceptions.
> Impala itself uses reload4j rather than log4j2, so this is purely about coordinating dependencies rather than Impala code.
> We should add dependency management for log4j-api and log4j-core. It makes sense to standardize on 2.18.0.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org