[IMPALA-13112] Remove Kafka Dependency Exclusion to Use KafkaAuditProvider #75
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dntjr8096
force-pushed
the
master
branch
3 times, most recently
from
971d347
to
a8d587c
Compare
|
Thanks for your contribution! We don't use pull requests in Apache Impala, we use Gerrit instead: https://gerrit.cloudera.org/. https://cwiki.apache.org/confluence/display/IMPALA/Using+Gerrit+to+submit+and+review+patches has a walkthrough for uploading patches for review. |
…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](apache@a1f4a84) 2. [Commit f85dbff](apache@f85dbff) Change-Id: I9a9cdab994552faa7b9d4c5da88d457dbd7b554d
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue : https://issues.apache.org/jira/browse/IMPALA-13112
Testing Environment:
The changes were tested in the following environment:
Results:
The tests confirmed that with the Kafka dependency exclusion removed:
Impala started successfully without any java.lang.NoClassDefFoundError errors related to javax.ws.rs.
Ranger's Kafka-based audit logging functioned correctly with the Kafka client included.
This change is expected to improve the integration between Impala and Ranger by enabling Kafka-based audit logging without reintroducing previous conflicts.