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

Posted to issues-all@impala.apache.org by "Michael Smith (Jira)" <ji...@apache.org> on 2025/09/18 21:09:00 UTC

[jira] [Comment Edited] (IMPALA-9601) Migrate Impala from log4j to log4j2

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

Michael Smith edited comment on IMPALA-9601 at 9/18/25 9:08 PM:
----------------------------------------------------------------

For the moment this has been postponed by switching to reload4j. According to https://reload4j.qos.ch/, they expect to produce maintenance releases for the foreseeable future.


was (Author: JIRAUSER288956):
For the moment this has been postponed by switching to reload4j.

> Migrate Impala from log4j to log4j2
> -----------------------------------
>
>                 Key: IMPALA-9601
>                 URL: https://issues.apache.org/jira/browse/IMPALA-9601
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Frontend
>    Affects Versions: Impala 4.0.0
>            Reporter: Joe McDonnell
>            Priority: Critical
>
> Impala currently uses log4j for logging. log4j has reached end of life and is not maintained. We need to migrate to using log4j2 for Impala's logging.
> Currently, it looks like we hook up log4j to log to glog through the GlogAppender:
> [https://github.com/apache/impala/blob/master/fe/src/main/java/org/apache/impala/util/GlogAppender.java]
> There may be configuration changes for the minicluster as well.



--
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