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

DBZ-1419 Avoiding redundancy in field definition

Browse Source
This commit is contained in:
Gunnar Morling 2019-08-20 08:25:51 +02:00
parent 0e39965c0e
commit cb66fdafdc
1 changed files with 3 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -912,16 +912,10 @@ public static EventProcessingFailureHandlingMode parse(String value) {
+ "point, both old and new binlog readers will be momentarily halted and new binlog reader will start that will read the binlog for all "
+ "configured tables. The parallel binlog reader will have a configured server id of 10000 + the primary binlog reader's server id.");
public static final Field TIME_PRECISION_MODE = Field.create("time.precision.mode")
.withDisplayName("Time Precision")
public static final Field TIME_PRECISION_MODE = RelationalDatabaseConnectorConfig.TIME_PRECISION_MODE
.withEnum(TemporalPrecisionMode.class, TemporalPrecisionMode.ADAPTIVE_TIME_MICROSECONDS)
.withWidth(Width.SHORT)
.withImportance(Importance.MEDIUM)
.withValidation(MySqlConnectorConfig::validateTimePrecisionMode)
.withDescription("Time, date, and timestamps can be represented with different kinds of precisions, including:"
+ "'adaptive_time_microseconds' (the default) like 'adaptive' mode, but TIME fields always use microseconds precision;"
+ "'connect' always represents time, date, and timestamp values using Kafka Connect's built-in representations for Time, Date, and Timestamp, "
+ "which uses millisecond precision regardless of the database columns' precision.");
.withValidation(MySqlConnectorConfig::validateTimePrecisionMode);
public static final Field BIGINT_UNSIGNED_HANDLING_MODE = Field.create("bigint.unsigned.handling.mode")
.withDisplayName("BIGINT UNSIGNED Handling")