fixing exception when setting mq.ssl.use.ibm.cipher.mappings for mq sink connector#74
Merged
Merged
Conversation
Joel-hanson
requested changes
Jul 21, 2025
Signed-off-by: A S Adil Mohammad <asadilmohammad2020@gmail.com>
added 2 commits
July 21, 2025 16:06
Signed-off-by: A S Adil Mohammad <asadilmohammad2020@gmail.com>
Signed-off-by: A S Adil Mohammad <asadilmohammad2020@gmail.com>
Signed-off-by: A S Adil Mohammad <asadilmohammad2020@gmail.com>
Joel-hanson
pushed a commit
that referenced
this pull request
Jul 23, 2025
- Fixes the issue of exception when setting mq.ssl.use.ibm.cipher.mappings. - In source code, the configuration CONFIG_NAME_MQ_SSL_USE_IBM_CIPHER_MAPPINGS is defined as Type.BOOLEAN but it was being used as: config.getString(MQSinkConfig.CONFIG_NAME_MQ_SSL_USE_IBM_CIPHER_MAPPINGS) Signed-off-by: A S Adil Mohammad <asadilmohammad2020@gmail.com> Signed-off-by: Joel Hanson <joelhanson025@gmail.com>
Joel-hanson
pushed a commit
to Joel-hanson/kafka-connect-mq-sink
that referenced
this pull request
May 29, 2026
- Fixes the issue of exception when setting mq.ssl.use.ibm.cipher.mappings. - In source code, the configuration CONFIG_NAME_MQ_SSL_USE_IBM_CIPHER_MAPPINGS is defined as Type.BOOLEAN but it was being used as: config.getString(MQSinkConfig.CONFIG_NAME_MQ_SSL_USE_IBM_CIPHER_MAPPINGS) Signed-off-by: A S Adil Mohammad <asadilmohammad2020@gmail.com> Signed-off-by: Joel Hanson <joelhanson025@gmail.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Signed-off-by: A S Adil Mohammad asadilmohammad2020@gmail.com
Description
This pull request fixes the issue of exception when setting mq.ssl.use.ibm.cipher.mappings.In source code, the configuration
CONFIG_NAME_MQ_SSL_USE_IBM_CIPHER_MAPPINGSis defined as Type.BOOLEAN but it was being used as:config.getString(MQSinkConfig.CONFIG_NAME_MQ_SSL_USE_IBM_CIPHER_MAPPINGS)Fixes #73
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Checklist