changelog/8.0/8.0.0/release_notes.md
This release complies with VEP-3 which removes the upgrade order requirement. Components can be upgraded in any order. It is recommended that the upgrade order should still be followed if possible, except to canary test the new version of VTGate before upgrading the rest of the components.
The following PRs made changes to behavior that clients might be relying on. They should be reviewed carefully so that client code can be changed in concert with a Vitess release deployment.
show tables where tables_in_db to use keyspace name, not underlying db name #6446SHOW (DATABASES|VITESS_SHARDS|VITESS_TABLETS) LIKE #6750Set statement support is added in Vitess. There are some system variables which are disabled by default and can be enabled using flag -enable_system_settings on VTGate.These system variables are set on the backing MySQL instance, and will force the connection to be dedicated instead of part of the connection pool.
Following PRs are experimental version of Vitess-native Orchestrator 'vtorc' is ready for users to try out.