. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 When not to Use Auto-Increment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . as much work as possible to the underlying MySQL instances. When this is not possible, Vitess will use a plan that collects input from multiple sources and merges the results to produce the correct query Documentation • VTGate Keyspace Graph The keyspace graph allows Vitess to decide which set of shards to use for a given keyspace, cell, and tablet type. 11 Partitions During horizontal resharding (splitting

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 When not to Use Auto-Increment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285 Planning to use Materialize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . table we want to shard using country. The lookup table will help us do that. Region Vindex We will use a region_json vindex to compute the keyspace_id for a customer row using the (id, country) fields.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Use Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 When not to Use Auto-Increment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346 Planning to use Materialize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Use Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 When not to Use Auto-Increment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388 Planning to use Materialize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Use Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 When not to Use Auto-Increment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365 Planning to use Materialize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Use Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 4 The use of unique keys 68 Which keys are eligible? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 When not to Use Auto-Increment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 When not to Use Auto-Increment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . shard resides. Keyspace Graph The keyspace graph allows Vitess to decide which set of shards to use for a given keyspace, cell, and tablet type. Partitions During horizontal resharding (splitting or table columns to sequence tables. If no value is specified for such a column, then VTGate will know to use the sequence table to generate a new value for it. VStream VStream is a change notification service

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 When not to Use Auto-Increment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . shard resides. Keyspace Graph The keyspace graph allows Vitess to decide which set of shards to use for a given keyspace, cell, and tablet type. Partitions During horizontal resharding (splitting or table columns to sequence tables. If no value is specified for such a column, then VTGate will know to use the sequence table to generate a new value for it. VStream VStream is a change notification system

boundary is the local file system. 10 Vitess Security Audit, 2023 . Compromising existing app Another use case of VTAdmin-web is to integrate it into an existing web app, where the existing web app already of vulnerabilities in public registries and assess whether projects use the vulnerable version. In either case, a threat actor can use a vulnerability in a 3rd-party dependency to escalate privileges and recommend adding a document on how to securely deploy and use VTAdmin. The purpose of this document is to provide a single source of actionable steps to use VTAdmin securely. The Vitess documentation currently

minimal reference client https://github.com/vitessio/messages was used as additional illustration of use-cases. ▪ branch master commit 7d2ac2189573a7d26cf0f42e17df749673e3d16f ◦ The testers received unencumbered the authentication schemes mentioned above, Vitess also implements MysqlDialog, which makes use of plain-text password comparison from both the server’s and the client’s perspectives. The problem pertained to the Vitess itself, while the rather minimal sample client called messages was employed as a use-case reference. The scope of the test was well-defined but not particularly extensive. Conversely