You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2026/04/01 03:03:00 UTC

[jira] [Updated] (FLINK-39372) Potential MySQL Binlog offset comparison failure after mysql-bin.999999

     [ https://issues.apache.org/jira/browse/FLINK-39372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated FLINK-39372:
-----------------------------------
    Labels: pull-request-available  (was: )

> Potential MySQL Binlog offset comparison failure after mysql-bin.999999
> -----------------------------------------------------------------------
>
>                 Key: FLINK-39372
>                 URL: https://issues.apache.org/jira/browse/FLINK-39372
>             Project: Flink
>          Issue Type: Improvement
>          Components: Flink CDC
>    Affects Versions: cdc-3.6.0
>            Reporter: Xiqian Yu
>            Assignee: Xiqian Yu
>            Priority: Major
>              Labels: pull-request-available
>
> MySQL CDC uses Java's String.compareTo() for comparing Binlog filenames. This works correctly for files like mysql.000001 through mysql.999999 since they share the same length.
> However, when the sequence rolls over to mysql.1000000, string comparison breaks — it treats '1' < '9' and incorrectly considers mysql.1000000 smaller than mysql.999999.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)