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 "Fang-Yu Rao (Jira)" <ji...@apache.org> on 2022/09/30 18:06:00 UTC
[jira] [Updated] (IMPALA-11632) Exclude log4j-1.2-api in some Ranger artifacts
[ https://issues.apache.org/jira/browse/IMPALA-11632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fang-Yu Rao updated IMPALA-11632:
---------------------------------
Description:
After RANGER-3498, Ranger's ranger-plugins-audit,
ranger-plugins-common, and -ranger-raz-hook-abfs- start pulling in log4j-1.2-api, which is currently banned by Impala's frontend. To be able to compile Impala after
RANGER-3498, we should excludes log4j-1.2-api when adding those Ranger dependencies mentioned above.
was:
After RANGER-3498, Ranger's ranger-plugins-audit,
ranger-plugins-common, and ranger-raz-hook-abfs start pulling in log4j-1.2-api, which is currently banned by Impala's frontend. To be able to compile Impala after
RANGER-3498, we should excludes log4j-1.2-api when adding those Ranger dependencies mentioned above.
> Exclude log4j-1.2-api in some Ranger artifacts
> ----------------------------------------------
>
> Key: IMPALA-11632
> URL: https://issues.apache.org/jira/browse/IMPALA-11632
> Project: IMPALA
> Issue Type: Task
> Components: Frontend
> Reporter: Fang-Yu Rao
> Assignee: Fang-Yu Rao
> Priority: Major
> Fix For: Impala 4.2.0
>
>
> After RANGER-3498, Ranger's ranger-plugins-audit,
> ranger-plugins-common, and -ranger-raz-hook-abfs- start pulling in log4j-1.2-api, which is currently banned by Impala's frontend. To be able to compile Impala after
> RANGER-3498, we should excludes log4j-1.2-api when adding those Ranger dependencies mentioned above.
--
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