ziyanTOP commented on code in PR #4413:
URL: https://github.com/apache/flink-cdc/pull/4413#discussion_r3322438859
##########
docs/content.zh/docs/connectors/flink-sources/mysql-cdc.md:
##########
@@ -441,6 +441,19 @@ Flink SQL> SELECT * FROM orders;
如果跳过 backfill ，快照阶段捕获表的更改将在稍后的 binlog 读取阶段被回放，而不是合并到快照中。<br>
警告：跳过 backfill 可能会导致数据不一致，因为快照阶段发生的某些 binlog 事件可能会被重放（仅保证
at-least-once ）。
例如，更新快照阶段已更新的值，或删除快照阶段已删除的数据。这些重放的 binlog 事件应进行特殊处理。
+ </td>
+ </tr>
+ <tr>
+ <td>scan.incremental.snapshot.string-key.compare-mode</td>
Review Comment:
Good point, but `collation_server` is just the server default — the actual
table or column can override it. To auto-detect properly we'd have to query
`information_schema.COLUMNS` per table at startup, and it gets messy with
composite PKs where each column might have a different collation.
So I went with explicit config for now — `default` keeps backward compat and
won't break anyone. We can add an `auto` mode later: detect each table's
chunk-key collation during snapshot, store it per-table in the split state, and
handle them individually
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
