In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.

Bug report

For bug reports, provide this information, please:

What Debezium connector do you use and what version?

MySQL connector Debezium 2.6 version

What is the connector configuration?

2.6

What is the captured database version and mode of depoyment?

(E.g. on-premises, with a specific cloud provider, etc.)

MySQL database service version 8.4 - oracle cloud 

What behaviour do you expect?

<Your answer>

What behaviour do you see?

MySQL connector fails. Producer  fails to stream. error message received

connect_1    | io.debezium.DebeziumException: Unexpected error while looking at GTID mode:

Do you see the same behaviour using the latest relesead Debezium version?

yes

Do you have the connector logs, ideally from start till finish?

(You might be asked later to provide DEBUG/TRACE level log)

connect_1    | 2024-06-24 04:59:07,331 INFO   MySQL|dbserver1|streaming  Starting streaming   [io.debezium.pipeline.ChangeEventSourceCoordinator]
connect_1    | 2024-06-24 04:59:07,346 ERROR  MySQL|dbserver1|streaming  Producer failure   [io.debezium.pipeline.ErrorHandler]
connect_1    | io.debezium.DebeziumException: Unexpected error while looking at GTID mode:
connect_1    |  at io.debezium.connector.mysql.strategy.mysql.MySqlConnection.knownGtidSet(MySqlConnection.java:61)
connect_1    |  at io.debezium.connector.mysql.MySqlStreamingChangeEventSource.execute(MySqlStreamingChangeEventSource.java:903)
connect_1    |  at io.debezium.connector.mysql.MySqlStreamingChangeEventSource.execute(MySqlStreamingChangeEventSource.java:76)
connect_1    |  at io.debezium.pipeline.ChangeEventSourceCoordinator.streamEvents(ChangeEventSourceCoordinator.java:280)
connect_1    |  at io.debezium.pipeline.ChangeEventSourceCoordinator.executeChangeEventSources(ChangeEventSourceCoordinator.java:197)
connect_1    |  at io.debezium.pipeline.ChangeEventSourceCoordinator.lambda$start$0(ChangeEventSourceCoordinator.java:140)
connect_1    |  at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
connect_1    |  at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
connect_1    |  at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
connect_1    |  at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
connect_1    |  at java.base/java.lang.Thread.run(Thread.java:829)
connect_1    | Caused by: java.sql.SQLSyntaxErrorException: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'MASTER STATUS' at line 1
connect_1    |  at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:121)
connect_1    |  at com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:122)
connect_1    |  at com.mysql.cj.jdbc.StatementImpl.executeQuery(StatementImpl.java:1208)
connect_1    |  at io.debezium.jdbc.JdbcConnection.queryAndMap(JdbcConnection.java:631)
connect_1    |  at io.debezium.jdbc.JdbcConnection.queryAndMap(JdbcConnection.java:500)
connect_1    |  at io.debezium.connector.mysql.strategy.mysql.MySqlConnection.knownGtidSet(MySqlConnection.java:53)

How to reproduce the issue using our tutorial deployment?

<Your answer>

Feature request or enhancement

Connector needs to work with MYSQL 8.4 version

Which use case/requirement will be addressed by the proposed feature?

<Your answer>

Implementation ideas (optional)

<Your answer>