From 971d347bbd9b5d68505c3930f45724f36fff2d8e Mon Sep 17 00:00:00 2001
From: "woosuk.ro" <lkjs8269@naver.com>
Date: Wed, 29 May 2024 17:28:45 +0900
Subject: [PATCH] [IMPALA-13112] Remove Kafka Dependency Exclusion to Use
 KafkaAuditProvider

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 a1f4a849cf1c4f51e0acc737c7da166651645870](https://github.com/apache/impala/commit/a1f4a849cf1c4f51e0acc737c7da166651645870)
2. [Commit f85dbff97618066d60f37736808c8c24aa0a98e5](https://github.com/apache/impala/commit/f85dbff97618066d60f37736808c8c24aa0a98e5)
---
 fe/pom.xml | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/fe/pom.xml b/fe/pom.xml
index 9dd29855a2..bb335fea7c 100644
--- a/fe/pom.xml
+++ b/fe/pom.xml
@@ -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.-->