terrymanu commented on issue #38894:
URL: 
https://github.com/apache/shardingsphere/issues/38894#issuecomment-4795879208

   Hi @penghuazhou, thanks for the question.
   
   Yes, MySQL 8.4.9 can be used from the compatibility perspective. According 
to the official MySQL documentation, MySQL 8.4.9 belongs to the MySQL 8.4 LTS 
series, MySQL supports upgrade paths from 8.0 to 8.4.x LTS, and MySQL 8.4 
continues to support binary-log-position based replication. For ShardingSphere 
Proxy migration, the `5.1.15 ~ 8.0.x` range in the current usage page looks 
like documentation that has not been updated yet, rather than proof that MySQL 
8.4.9 is incompatible.
   
   Relevant official MySQL documents:
   
   - MySQL 8.4.9 Release Notes: 
https://dev.mysql.com/doc/relnotes/mysql/8.4/en/news-8-4-9.html
   - MySQL Releases: Innovation and LTS: 
https://dev.mysql.com/doc/refman/8.4/en/mysql-releases.html
   - MySQL 8.4 Upgrade Paths: 
https://dev.mysql.com/doc/refman/8.4/en/upgrade-paths.html
   - MySQL 8.4 Replication: 
https://dev.mysql.com/doc/refman/8.4/en/replication.html
   - Replication Compatibility Between MySQL Versions: 
https://dev.mysql.com/doc/refman/8.4/en/replication-compatibility.html
   - Connector/J 8.4.0 Release Notes: 
https://dev.mysql.com/doc/relnotes/connector-j/en/news-8-4-0.html
   - Native Pluggable Authentication in MySQL 8.4: 
https://dev.mysql.com/doc/refman/8.4/en/native-pluggable-authentication.html
   
   Please use `mysql-connector-j-8.4.0.jar` or a newer compatible MySQL 
Connector/J, keep the normal migration requirements such as binlog and 
permissions configured, and use the default `caching_sha2_password` 
authentication or explicitly configure `mysql_native_password` if your account 
depends on it. If you meet a concrete runtime error with MySQL 8.4.9, please 
provide the ShardingSphere version, Proxy migration configuration, MySQL 
account authentication plugin, and the error log so we can analyze it as a 
specific bug.
   
   I suggest labeling this as `type: question` and closing it once the answer 
is clear.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to