. . . . . . . . . . . . . . . 413 Upgrading Vitess . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413 Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . 413 Upgrade Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413 Canary Testing . . . . . . . . . the release notes): • vttablet • vtctld • vtgate • application code which links client libraries 413 Canary Testing Within the vtgate and vttablet components, we recommend to canary single instances

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413 Unsharded Keyspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Since the table is not sharded, we have a trivial VSchema addition: "corder_keyspace_idx": {} 413 We can now instantiate the Lookup Vindex in the VSchema of the customer keyspace: "corder_keyspace_idx":

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413 Managed, Online Schema Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . declarative migration which ends up being a noop (and implicitly successful), implies a noop revert. 413 Managed, Online Schema Changes Note: this feature is EXPERIMENTAL. Vitess offers managed, online

keyspace as a database. Under the covers, the MySQL database backing it is actually vt_commerce. 413 Congratulations! You have successfully brought up a Vitess cluster. vtorc (experimental) vtorc is