From 885d72b6d39b665326afd8e89475960b19f7de36 Mon Sep 17 00:00:00 2001 From: Aolin Date: Tue, 4 Jul 2023 12:07:28 +0800 Subject: [PATCH] Apply suggestions from code review Co-authored-by: xixirangrang --- ticdc/ticdc-integrity-check.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ticdc/ticdc-integrity-check.md b/ticdc/ticdc-integrity-check.md index 2ea50c78213e4..36a271dbc942a 100644 --- a/ticdc/ticdc-integrity-check.md +++ b/ticdc/ticdc-integrity-check.md @@ -100,5 +100,5 @@ For more information about the implementation of data consumption and checksum v > **Note:** > -> - After enabling the checksum validation feature, DECIMAL and UNSIGNED BIGINT types data will be converted to string types. Therefore, in the downstream consumer code, you need to convert them back to their corresponding numerical types before calculating checksum values. -> - The checksum verification process does not include delete events. This is because delete events only contain the handle key column, while the checksum is calculated based on all columns. +> - After enabling the checksum validation feature, DECIMAL and UNSIGNED BIGINT types data will be converted to STRING types. Therefore, in the downstream consumer code, you need to convert them back to their corresponding numerical types before calculating checksum values. +> - The checksum verification process does not include DELETE events. This is because DELETE events only contain the handle key column, while the checksum is calculated based on all columns.