-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make built in ErrorSender plugin use kafka security params #2028
Labels
Comments
Zejnilovic
added
bug
Something isn't working
priority: undecided
Undecided priority to be assigned after discussion
labels
Mar 11, 2022
dk1844
added a commit
that referenced
this issue
Mar 11, 2022
dk1844
added a commit
that referenced
this issue
Mar 17, 2022
…via spark.executorEnv (+unit test) - todo test this
dk1844
added a commit
that referenced
this issue
Mar 17, 2022
…via spark.executor.extraJavaOptions (+unit test) - todo test this
dk1844
added a commit
that referenced
this issue
Mar 18, 2022
dk1844
added a commit
that referenced
this issue
Mar 22, 2022
…p` to `SecureConfig.javaOptsStringFromConfigMap` (unit tests adjusted)
dk1844
added a commit
that referenced
this issue
Mar 22, 2022
… params (#2029) * #2028 bugfix: kafka error sender now support schema registry security params * #2028 trustStore/keyStore params passing to kafka producers - passed via spark.executor.extraJavaOptions (+unit test) - * #2028 SecureConfig methods redone + unit test * #2028 license check fix * #2028 PR review: Moved `CommonJobExecution.javaOptsStringFromConfigMap` to `SecureConfig.javaOptsStringFromConfigMap` (unit tests adjusted)
Release notes: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Describe the bug
Currently, only the info sender plugin leverages the Kafka security params
Expected behavior
Error Sender plugin also uses kafka security params
The text was updated successfully, but these errors were encountered: