fixing exception when setting mq.ssl.use.ibm.cipher.mappings for mq sink connector #74
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