From a2f15abafdc1c07395cd3765c3fb9c984c39e6dc Mon Sep 17 00:00:00 2001 From: Henry Cai Date: Mon, 30 Jan 2023 15:56:29 -0800 Subject: [PATCH] DBZ-6043: Vitess: Support Mapping unsigned bigint mysql column type to long Add doc for the new `bigint.unsigned.handling.mode` --- .../modules/ROOT/pages/connectors/vitess.adoc | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/documentation/modules/ROOT/pages/connectors/vitess.adoc b/documentation/modules/ROOT/pages/connectors/vitess.adoc index a8ca84b17..5994887cc 100644 --- a/documentation/modules/ROOT/pages/connectors/vitess.adoc +++ b/documentation/modules/ROOT/pages/connectors/vitess.adoc @@ -1335,6 +1335,20 @@ When the connector starts, if it does not detect a value in its offsets topic, i `never`:: When the connector starts, it skips the snapshot process and immediately begins to stream change events for operations that the database records to the binary logs. + +|[[vitess-property-bigint-unsigned-handling-mode]]<> +|string +|Specify how BIGINT UNSIGNED columns should be represented in change events. + +Set the property to one of the following values: + + + +`string`:: + +represent values using Java's `string` + + + +`long`:: + +represents values using Java's `long`, which may not offer the precision but will be far easier to use in consumers. + + + +`precise`:: + +represents values as precise (Java's 'BigDecimal') values. This is precise but difficult to use. |=== [id="vitess-advanced-configuration-properties"]