[Bug] [mysql-cdc] stop.mode = 'specific' Not Worked.

[wevyisub]

Search before asking

• I had searched in the issues and found no similar issues.

What happened

Testing to use the Mysql-cdc module for incremental loading.
However, it seems that 'stop.mode' does not work normally.

The start position of the bin log was set to 'start.mode', and the end position was set to 'stop.mode'.
However, even though the binlog location specified in stop.mode has passed, the job does not end and continues.

SeaTunnel Version

2.3.4

SeaTunnel Config

env {
  job.mode = "STREAMING"
  checkpoint.interval = 20000
}

source {
   MySQL-CDC {
    parallelism = 1
    server-id = 5656
    username = "test"
    password = "test"
    table-names = ["cdc.cdc_full_columns"]
    base-url = "jdbc:mysql://localhost:3306/cdc"
    format = "compatible_debezium_json"
    debezium = {
        key.converter.schemas.enable = false
        value.converter.schemas.enable = false
        include.schema.changes = true
        database.server.name =  "mysql_cdc_1"
    }
    startup.mode = "specific"
    startup.specific-offset.file = "mysql-bin.000003"
    startup.specific-offset.pos = "5372"
    stop.mode = "specific"
    stop.specific-offset.file = "mysql-bin.000003"
    stop.specific-offset.pos = "8070"
    
  }
}

sink {
  Console {
  }

}

Running Command

./bin/seatunnel.sh --config ./config/v2.streaming.conf.template

Error Exception

no error. 
It does not end even after reaching the position designated as 'stop.mode'.

Zeta or Flink or Spark Version

zeta

Java or Scala Version

java 1.8

Screenshots

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct