You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This project has been tested and confirmed to work with MySQL versions up to 8.0.4.
However, for users attempting to use this library with MySQL 8.4 or later, there is a compatibility issue.
The SHOW MASTER STATUS query, which is used in the binlogstream.py file, is deprecated in MySQL 8.4 and replaced by SHOW BINARY LOG STATUS.
As a result, when running the library with MySQL 8.4 or newer versions, the SHOW MASTER STATUS query will fail
The text was updated successfully, but these errors were encountered:
Yeah sure. It seems the MySQL team is officially updating their terminology, so the syntax is gradually changing...
However, I'm curious whether there are plans to maintain this project to support MySQL 8.4 and above.
If we're just looking to resolve this immediate issue, we could implement a version check and use different queries accordingly.
Though I haven't verified it myself yet, I wonder if there might be other issues due to features that have been removed or deprecated in version 8.4? https://dev.mysql.com/doc/refman/8.4/en/mysql-nutshell.html#mysql-nutshell-deprecations
@why-arong
It seems the best approach is to handle it by branching the logic for versions before and after 8.4.
It seems that many Master commands are being removed in version 8.4. I’ll investigate how these commands are being used in our project.
Description:
This project has been tested and confirmed to work with MySQL versions up to 8.0.4.
However, for users attempting to use this library with MySQL 8.4 or later, there is a compatibility issue.
The
SHOW MASTER STATUS
query, which is used in thebinlogstream.py
file, is deprecated in MySQL 8.4 and replaced bySHOW BINARY LOG STATUS
.As a result, when running the library with MySQL 8.4 or newer versions, the SHOW MASTER STATUS query will fail
The text was updated successfully, but these errors were encountered: