Florent Poinsard
Florent Poinsard
This is a follow up of https://github.com/vitessio/vitess/pull/17641.
## Description This PR adds query planning support for the new BlockJoin execution strategy, as proposed in the [RFC](https://github.com/vitessio/vitess/issues/16508). We’ve also streamlined the engine primitive, starting with a minimal implementation...
https://github.com/vitessio/vitess/blob/516b85487dcca2943bdeb7e3211a4adc77991d93/go/tools/go-upgrade/go-upgrade.go#L454-L456 This snippet of code only checks for a change in the major and minor version of Go, not looking at the patch number. Which leads the go-upgrade tool to...
## Context This issue tracks all the work for the `v22.0.0` release, including RCs, code freeze, and GA. The version `2.15.0` of the vitess-operator will be released at the same...
Make sure we use the right version
Note to myself: once the next release (`v2.15.0`) is out, we should do that check before and after we upgrade. _Originally posted by @frouioui in https://github.com/planetscale/vitess-operator/pull/629#discussion_r1836896569_
The default behavior of the manual failover is to shutdown the current primary using a graceful (`fast`) shutdown. This approach is more than valid and should be used in most...
As reported in https://github.com/planetscale/vitess-operator/issues/710, when a keyspace had keyspace-level image definition in its spec, it would overwirte the cluster-level image definition for any subsequent keyspaces. This PR fixes https://github.com/planetscale/vitess-operator/issues/710 by...