[FLINK-38934][cdc connector mysql] honour ssl protocol setting configured in debeziumProps #4225
Conversation
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
…ured in debeziumProps
github-actions
bot
added
docs
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
https://issues.apache.org/jira/browse/FLINK-38934
What is the purpose of the change
Add support for configuring the TLS protocol used by the binlog client via
debezium.binlog.ssl.protocolUse case: Allow users to specify the tls version used by the binlog client.
One example use caseWorkaround for FLINK-38904 (TLS 1.3 KeyUpdate deadlock) by allowing users to force TLSv1.2 for the binlog connection.
Example:
'debezium.binlog.ssl.protocol' = 'TLSv1.2'
Changes
Use the protocol provided in
debezium.binlog.ssl.protocolfor binlog client connection.