[
https://issues.apache.org/jira/browse/IMPALA-13112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18052783#comment-18052783
]
ASF subversion and git services commented on IMPALA-13112:
----------------------------------------------------------
Commit 3e29f8aaa8f1a02630505866de45a918918aa216 in impala's branch
refs/heads/master from woosuk.no
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=3e29f8aaa ]
IMPALA-13112: Remove Kafka exclusion from ranger-plugins-audit
Previously, Impala excluded Kafka dependencies from ranger-plugins-audit
to avoid JAX-RS conflicts that caused java.lang.NoClassDefFoundError:
javax/ws/rs/core/Link$Builder errors. These exclusions were added in
commits a1f4a849 and f85dbff9.
Recent testing shows that kafka-clients-2.8.1.jar, which is now used
by Apache Ranger, no longer causes these JAX-RS version conflicts.
Removing the Kafka exclusion is necessary to enable Ranger's
kafkaAuditProvider for comprehensive audit logging capabilities.
This patch removes the Kafka dependency exclusions from the
ranger-plugins-audit dependency in fe/pom.xml, re-enabling
Kafka-based audit logging in Ranger.
Testing:
- Verified no JAX-RS conflicts in Impala 4.4.0 with Hive 3.1.3
- Confirmed Ranger kafkaAuditProvider functions correctly
- All existing tests pass
Change-Id: I8a4dbb8106106a45443a8c74d716cdebb213a0cf
Reviewed-on: http://gerrit.cloudera.org:8080/23675
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Remove Kafka Dependency Exclusion from ranger-plugins-audit in Impala FE
> pom.xml
> --------------------------------------------------------------------------------
>
> Key: IMPALA-13112
> URL: https://issues.apache.org/jira/browse/IMPALA-13112
> Project: IMPALA
> Issue Type: Improvement
> Components: Frontend
> Affects Versions: Impala 4.1.0, Impala 4.2.0, Impala 4.1.1, Impala 4.1.2,
> Impala 4.3.0, Impala 4.4.0
> Reporter: woosuk.ro
> Assignee: woosuk.ro
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> h4. Background:
> Previously, Impala removed the Kafka dependency from the
> {{ranger-plugins-audit}} module due to conflicts with the JAX-RS package.
> This conflict resulted in errors like {{{}java.lang.NoClassDefFoundError:
> javax/ws/rs/core/Link$Builder{}}}. Relevant commits include:
> # [Commit
> a1f4a849cf1c4f51e0acc737c7da166651645870|https://github.com/apache/impala/commit/a1f4a849cf1c4f51e0acc737c7da166651645870]
> # [Commit
> f85dbff97618066d60f37736808c8c24aa0a98e5|https://github.com/apache/impala/commit/f85dbff97618066d60f37736808c8c24aa0a98e5]
> These commits addressed the issue by excluding all Kafka dependencies to
> avoid JAX-RS version conflicts, specifically related to {{kafka_2.11}} and
> later {{{}kafka_2.12{}}}.
> h4. Current Situation:
> Recent tests indicate that the latest version of {{kafka-clients-2.8.1.jar}}
> used by Apache Ranger no longer causes the previous JAX-RS conflicts.
> Therefore, we propose to remove the exclusion of Kafka dependencies from
> {{ranger-plugins-audit}} in Impala's {{{}pom.xml{}}}. This change is
> necessary to utilize Ranger's {{{}kafkaAuditProvider{}}}, which requires
> Kafka clients.
> h4. Proposal:
> Modify the {{pom.xml}} file in Impala FE to remove the Kafka dependency
> exclusion from {{{}ranger-plugins-audit{}}}. This update will re-enable the
> Kafka-based audit logging capabilities in Ranger, which is essential for
> comprehensive audit logging.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
