Skip to content

Commit

Permalink
[IMPALA-13112] Remove Kafka Dependency Exclusion to Use KafkaAuditPro…
Browse files Browse the repository at this point in the history
…vider

Recent tests indicate that the latest version of `kafka-clients-2.8.1.jar`
used by Apache Ranger does not cause the previous JAX-RS conflicts.
Therefore, this exclusion is no longer necessary. Removing the exclusion
allows us to use the KafkaAuditProvider in Ranger for comprehensive audit
logging.

References:
1. [Commit a1f4a84](a1f4a84)
2. [Commit f85dbff](f85dbff)
  • Loading branch information
dntjr8096 authored and woosukro committed May 29, 2024
1 parent 2e093bb commit 971d347
Showing 1 changed file with 0 additions and 4 deletions.
4 changes: 0 additions & 4 deletions fe/pom.xml
Original file line number Diff line number Diff line change
Expand Up @@ -176,10 +176,6 @@ under the License.
<groupId>com.cloudera</groupId>
<artifactId>jwtprovider-knox</artifactId>
</exclusion>
<exclusion>
<groupId>org.apache.kafka</groupId>
<artifactId>*</artifactId>
</exclusion>
<!-- After RANGER-3498, Ranger's ranger-plugins-audit starts pulling in
log4j-1.2-api, which is banned by Impala's frontend. Thus we exclude the
dependency here.-->
Expand Down

0 comments on commit 971d347

Please sign in to comment.