alexey.rassokhin/tet123
1
0
Fork 0
Code Issues Pull Requests 1 Packages Projects Releases Wiki Activity

fix GTID_NEW_CHANNEL_POSITION description

Browse Source
This commit is contained in:
Eero Koplimets 2018-11-01 12:15:53 +02:00 committed by Gunnar Morling
parent 268101acd5
commit 3e1eaef318
1 changed files with 4 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
debezium-connector-mysql/src/main/java/io/debezium/connector/mysql/MySqlConnectorConfig.java
View File

@ -740,13 +740,11 @@ public static DdlParsingMode parse(String value, String defaultValue) {
.withDescription("If set to true, we will only produce DML events into Kafka for transactions that were written on mysql servers with UUIDs matching the filters defined by the gtid.source.includes or gtid.source.excludes configuration options, if they are specified.");
/**
* If set to true, connector when encountering new GTID channel after job restart will start reading it from the
* latest executed position (default). When set to false the connector will try to read this GTID channel from the first available offset.
* This is useful when in active-passive mysql setup during failover new GTID channel gets used, see #DBZ-923
* If set to 'latest', connector when encountering new GTID channel after job restart will start reading it from the
* latest executed position (default). When set to 'earliest' the connector will start reading new GTID channels from the first available position.
* This is useful when in active-passive mysql setup during failover new GTID channel starts receiving writes, see #DBZ-923
*
* Defaults to true.
*
* When true, either {@link #GTID_SOURCE_INCLUDES} or {@link #GTID_SOURCE_EXCLUDES} must be set.
* Defaults to latest.
*/
public static final Field GTID_NEW_CHANNEL_POSITION = Field.create("gtid.new.channel.position")
.withDisplayName("GTID start position")