MySQL 8.4 removes several SQL commands that Debezium uses to determine binlog position.

From my observation the only affected file should be `MySqlSnapshotChangeEventSource.java`. I have not observed if MariaDB has some similar changes.

MySQL 8.4 changelog – https://dev.mysql.com/doc/relnotes/mysql/8.4/en/news-8-4-0.html

Bug report

For bug reports, provide this information, please:

What Debezium connector do you use and what version?

2.6.1.Final but issue still remains in 2.7.0.Alpha1

What is the connector configuration?

No effect on the issue

What is the captured database version and mode of depoyment?

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

MySQL 8.4

What behaviour do you expect?

Connector should stream without an issue

What behaviour do you see?

Connector failing

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

(Ideally, also verify with latest Alpha/Beta/CR version)

Yes

Implementation ideas (optional)

Query MySQL version before checking the MASTER STATUS with

SHOW VARIABLES LIKE "%version%";

Once the version is queried, decide what SQL query is correct fit for specific MySQL implementation. From documentation it seems that only thing that hanges is the actual naming of query, not it's return.