Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

update v16 release notes about VTGate Advertised MySQL Version #12957

Merged
merged 3 commits into from
Apr 25, 2023
Merged

update v16 release notes about VTGate Advertised MySQL Version #12957

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c5f8e75
update v16 release notes about VTGate Advertised MySQL Version
yoheimuta Apr 24, 2023
b16a3df
Update changelog/16.0/16.0.0/release_notes.md
frouioui Apr 24, 2023
960625e
Update changelog/16.0/16.0.0/summary.md
frouioui Apr 24, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions changelog/16.0/16.0.0/release_notes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -109,6 +109,8 @@ or
Since [Pull Request #11989](https://github.com/vitessio/vitess/pull/11989), VTGate advertises MySQL version 8.0.30. This is a breaking change for clients that rely on the VTGate advertised MySQL version and still use MySQL 5.7.
The users can set the `mysql_server_version` flag to advertise the correct version.

It's worth noting that [the feature to avoid using reserved connections](https://vitess.io/docs/16.0/reference/query-serving/reserved-conn/#avoiding-the-use-of-reserved-connections) depends on the `mysql_server_version`, which has been changed from `5.7.9-vitess` to `8.0.30-Vitess` as the default value from now on. In conclusion, we recommend that users running MySQL 5.7 set vtgate's `mysql_server_version` to `5.7.9-vitess` to prevent the queries from being unexpectedly rewritten.
frouioui marked this conversation as resolved.
Show resolved Hide resolved

#### <a id="default-mysql-version"/>Default MySQL version on Docker

The default major MySQL version used by our `vitess/lite:latest` image is going from `5.7` to `8.0`. Additionally, the patch version of MySQL80 has been upgraded from `8.0.23` to `8.0.30`.
Expand Down
2 changes: 2 additions & 0 deletions changelog/16.0/16.0.0/summary.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -108,6 +108,8 @@ or
Since [Pull Request #11989](https://github.com/vitessio/vitess/pull/11989), VTGate advertises MySQL version 8.0.30. This is a breaking change for clients that rely on the VTGate advertised MySQL version and still use MySQL 5.7.
The users can set the `mysql_server_version` flag to advertise the correct version.

It's worth noting that [the feature to avoid using reserved connections](https://vitess.io/docs/16.0/reference/query-serving/reserved-conn/#avoiding-the-use-of-reserved-connections) depends on the `mysql_server_version`, which has been changed from `5.7.9-vitess` to `8.0.30-Vitess` as the default value from now on. In conclusion, we recommend that users running MySQL 5.7 set vtgate's `mysql_server_version` to `5.7.9-vitess` to prevent the queries from being unexpectedly rewritten.
frouioui marked this conversation as resolved.
Show resolved Hide resolved

#### <a id="default-mysql-version"/>Default MySQL version on Docker

The default major MySQL version used by our `vitess/lite:latest` image is going from `5.7` to `8.0`. Additionally, the patch version of MySQL80 has been upgraded from `8.0.23` to `8.0.30`.
Expand Down