. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Basic Flow for version tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Online DDL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492 Migration flow and states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501 Stateless flow by table name hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Basic Flow for version tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Stateless flow by table name hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Online DDL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439 Migration flow and states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Basic Flow for version tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Stateless flow by table name hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Online DDL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415 Migration flow and states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Basic Flow for version tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Stateless flow by table name hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375 Migration flow and states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313 Migration flow and states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Client APIs account for sharding operations.— ## Table lifecycle Vitess manages a table lifecycle flow, an abstraction and automation for a DROP TABLE operation. Problems with DROP TABLE Vitess inherits following stages or some subset: in use -> hold -> purge -> evac -> drop -> removed To understand the flow better, consider the following breakdown: • In use: the table is serving traffic, like a normal table

obtained an actor from the incoming request, VTAdmin validates the actor against the RBAC. As such, the flow of handling the permissions of incoming requests looks as such: Authentication Authentication in

the keyspace graph supports keyspace redirects, called ServedFrom records. That enables a migration flow like this: 1. Create new_keyspace and set its ServedFrom to point to old_keyspace. 2. Update the

the keyspace graph supports keyspace redirects, called ServedFrom records. That enables a migration flow like this: 1. Create new_keyspace and set its ServedFrom to point to old_keyspace. 2. Update the

the keyspace graph supports keyspace redirects, called ServedFrom records. That enables a migration flow like this: 1. Create new_keyspace and set its ServedFrom to point to old_keyspace. 2. Update the