Bug fix: Handle missing shade config overwrites for Kafka #13437
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.
After multiple shading changes, we had started appending
org.apache.pinot.shaded
to the Kafka classpaths that were mentioned in the table config so that we don't run into ClassNotFound errors.This was done in #13087 amd #13056
However, sometimes these classpaths can also be mentioned in the
jaas
configs in which case they are not updated and hence we still get ClassNotFound errorThis PR adds a way to rename these classapth and also make them part of the table config since ovewriting jaas config file is not correct from security perspective.