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

Posted to dev@ranger.apache.org by "kirby zhou (Jira)" <ji...@apache.org> on 2022/04/24 02:54:00 UTC

[jira] [Commented] (RANGER-3730) log4j dependency is not completely removed

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

kirby zhou commented on RANGER-3730:
------------------------------------

log4j2.version is useful.

1. elasticsearch use log4j2 as its logger, so we need use a bridge log4j-slf4j-impl:${log4j2.version} in 

ranger-elasticsearch-plugin-shim.

see https://issues.apache.org/jira/browse/RANGER-3696

2. Embeddedwebserver and security-admin want to call elastisearch to store audit, so it should provide a bridge log4j-to-slf4j and log4j-api for elasticsearch.

 

log4j.version seem useful too

It is only used by knox-agent in test scope, and knox use log4j, knox-agent runs inside knox actually be with log4j, we should test it.

 

> log4j dependency is not completely removed
> ------------------------------------------
>
>                 Key: RANGER-3730
>                 URL: https://issues.apache.org/jira/browse/RANGER-3730
>             Project: Ranger
>          Issue Type: Bug
>          Components: Ranger
>    Affects Versions: 3.0.0, 2.3.0
>            Reporter: Bhavik Patel
>            Priority: Major
>
> log4j dependency is present in parent pom file - [https://github.com/apache/ranger/blob/master/pom.xml#L166]
>  
> [~madhan]  [~ma3mansoori123] 



--
This message was sent by Atlassian Jira
(v8.20.7#820007)