installation, let’s start with the global cell service. It is described by the addresses of the servers (comma separated list), and by the root directory to put the Vitess data in. For instance, assuming we want installation, let’s start with the global cell service. It is described by the addresses of the servers (comma separated list), and by the root directory to put the Vitess data in. For instance, assuming we want • max_tps: 99999, reserved. • max_replication_lag: 99999, reserved. • tablet_types: specifies a comma separated list of tablet types to replicate from. If empty, the default tablet type specified by the

installation, let’s start with the global cell service. It is described by the addresses of the servers (comma separated list), and by the root directory to put the Vitess data in. For instance, assuming we want installation, let’s start with the global cell service. It is described by the addresses of the servers (comma separated list), and by the root directory to put the Vitess data in. For instance, assuming we want • max_tps: 99999, reserved. • max_replication_lag: 99999, reserved. • tablet_types: specifies a comma separated list of tablet types to replicate from. If empty, the default tablet type specified by the

installation, let’s start with the global cell service. It is described by the addresses of the servers (comma separated list), and by the root directory to put the Vitess data in. For instance, assuming we want installation, let’s start with the global cell service. It is described by the addresses of the servers (comma separated list), and by the root directory to put the Vitess data in. For instance, assuming we want • max_tps: 99999, reserved. • max_replication_lag: 99999, reserved. • tablet_types: specifies a comma separated list of tablet types to replicate from. If empty, the default tablet type specified by the

Specifies the names of the keyspaces to be created as a comma separated value. NUM_SHARDS yes Specifies the number of shards in each keyspace. It is a comma separated value as well, read in conjunction with installation, let’s start with the global cell service. It is described by the addresses of the servers (comma separated list), and by the root directory to put the Vitess data in. For instance, assuming we want installation, let’s start with the global cell service. It is described by the addresses of the servers (comma separated list), and by the root directory to put the Vitess data in. For instance, assuming we want

installation, let’s start with the global cell service. It is described by the addresses of the servers (comma separated list), and by the root directory to put the Vitess data in. For instance, assuming we want installation, let’s start with the global cell service. It is described by the addresses of the servers (comma separated list), and by the root directory to put the Vitess data in. For instance, assuming we want URLs - empty means allow all for anyone (built-in policies: deny-all, read-only) service_map value comma separated list of services to enable (or disable if prefixed with ‘-’) Example: grpc-vtworker sql-max-length-errors

above: • source_unique_key_columns is the (comma delimited) list of columns covered by the chosen key on source table • target_unique_key_columns is the (comma delimited) list of columns covered by the the chosen key on target table • source_unique_key_target_columns is the (comma delimited) list of column names in target table, which map to source_unique_key_columns. This mapping is necessary because columns umns:"order_id ,customer_id" } } Not much changed from the previous example, just note how we comma separate "order_id,customer_id" Example 3 Continuing previous example, we now rename a column the

installation, let’s start with the global cell service. It is described by the addresses of the servers (comma separated list), and by the root directory to put the Vitess data in. For instance, assuming we want installation, let’s start with the global cell service. It is described by the addresses of the servers (comma separated list), and by the root directory to put the Vitess data in. For instance, assuming we want • max_tps: 99999, reserved. • max_replication_lag: 99999, reserved. • tablet_types: specifies a comma separated list of tablet types to replicate from. If empty, the default tablet type specified by the

installation, let’s start with the global cell service. It is described by the addresses of the servers (comma separated list), and by the root directory to put the Vitess data in. For instance, assuming we want installation, let’s start with the global cell service. It is described by the addresses of the servers (comma separated list), and by the root directory to put the Vitess data in. For instance, assuming we want • max_tps: 99999, reserved. • max_replication_lag: 99999, reserved. • tablet_types: specifies a comma separated list of tablet types to replicate from. If empty, the default tablet type specified by the