[
https://issues.apache.org/jira/browse/IMPALA-14824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18080477#comment-18080477
]
ASF subversion and git services commented on IMPALA-14824:
----------------------------------------------------------
Commit f5df49ec765ee2f3fd0226b5746e209b0d04432b in impala's branch
refs/heads/master from Csaba Ringhofer
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=f5df49ec7 ]
IMPALA-14824: Replace remaining log4j usage with slf4j
Exceptions where log4j only functions are used:
- JvmPauseMonitor: LOG.fatal()
- ImpalaJdbcClient: LOG.addAppender()
These exceptions are ok as the goal is more consistancy
and not to remove log4j dependency.
Generated-by: Claude Sonnet 4.6
Change-Id: Id3ab02468db13ed6e37cac7b6ab74841317a9e6e
Reviewed-on: http://gerrit.cloudera.org:8080/24223
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Replace remaining log4j logging with slf4j
> ------------------------------------------
>
> Key: IMPALA-14824
> URL: https://issues.apache.org/jira/browse/IMPALA-14824
> Project: IMPALA
> Issue Type: Task
> Components: Catalog, Frontend
> Reporter: Csaba Ringhofer
> Priority: Major
> Labels: ramp-up
>
> Most of Java classes in Impala use org.slf4j.Logger (253 files) some use
> import org.apache.log4j.Logger (35 files). It would be better to be
> consistent + stop log4j usage spreading through copy paste.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
