tmp_table_size ReservedConn transaction_prealloc_size ReservedConn unique_checks ReservedConn updatable_views_with_limit ReservedConn binlog_format CheckAndIgnore block_encryption_mode CheckAndIgnore character_set_client unsharded to an unsharded keyspace using a different vindex than the source keyspace. • Materialized Views: You can specify a materialization rule that creates a view of the source table into a target keyspace For example, it can be used to control the cut-over during resharding. In the case of materialized views, it can be used to establish equivalence of tables, which will allow VTGate to compute the most optimal

tmp_table_size ReservedConn transaction_prealloc_size ReservedConn unique_checks ReservedConn updatable_views_with_limit ReservedConn binlog_format CheckAndIgnore block_encryption_mode CheckAndIgnore character_set_client not overload the primary. • We issue a DELETE FROM my_table LIMIT 50 ; 10-100 are normally good chunk sizes. Order of purging does not matter. 47 It’s important to note that the DELETE statement actually unsharded to an unsharded keyspace using a different vindex than the source keyspace. • Materialized Views: You can specify a materialization rule that creates a view of the source table into a target keyspace

tmp_table_size ReservedConn transaction_prealloc_size ReservedConn unique_checks ReservedConn updatable_views_with_limit ReservedConn binlog_format CheckAndIgnore block_encryption_mode CheckAndIgnore character_set_client not overload the primary. • We issue a DELETE FROM my_table LIMIT 50 ; 10-100 are normally good chunk sizes. Order of purging does not matter. It’s important to note that the DELETE statement actually GetSchema GetSchema [-tables=,,...] [-exclude_tables=,,...] [-include-views] ReloadSchema ReloadSchema ReloadSchemaShard ReloadSchemaShard [-concurrency=10]

tmp_table_size ReservedConn transaction_prealloc_size ReservedConn unique_checks ReservedConn updatable_views_with_limit ReservedConn binlog_format CheckAndIgnore block_encryption_mode CheckAndIgnore character_set_client not overload the primary. • We issue a DELETE FROM my_table LIMIT 50 ; 10-100 are normally good chunk sizes. Order of purging does not matter. It’s important to note that the DELETE statement actually GetSchema GetSchema [-tables=,,...] [-exclude_tables=,,...] [-include-views] ReloadSchema ReloadSchema ReloadSchemaShard ReloadSchemaShard [-concurrency=10]

tmp_table_size ReservedConn transaction_prealloc_size ReservedConn unique_checks ReservedConn updatable_views_with_limit ReservedConn binlog_format CheckAndIgnore block_encryption_mode CheckAndIgnore 27 System not overload the primary. • We issue a DELETE FROM my_table LIMIT 50 ; 10-100 are normally good chunk sizes. Order of purging does not matter. It’s important to note that the DELETE statement actually GetSchema GetSchema [-tables=,,...] [-exclude_tables=,,...] [-include-views] ReloadSchema ReloadSchema ReloadSchemaShard ReloadSchemaShard [-concurrency=10]

unsharded to an unsharded keyspace using a different vindex than the source keyspace. • Materialized Views: You can specify a materialization rule that creates a view of the source table into a target keyspace For example, it can be used to control the cut-over during resharding. In the case of materialized views, it can be used to establish equivalence of tables, which will allow VTGate to compute the most optimal chunks. After each chunk is copied, replication is resumed until it’s caught up. VReplication ensures that only changes that affect existing rows are applied. Following this another chunk is copied, and so

unsharded to an unsharded keyspace using a different vindex than the source keyspace. • Materialized Views: You can specify a materialization rule that creates a view of the source table into a target keyspace For example, it can be used to control the cut-over during resharding. In the case of materialized views, it can be used to establish equivalence of tables, which will allow VTGate to compute the most optimal chunks. After each chunk is copied, replication is resumed until it’s caught up. VReplication ensures that only changes that affect existing rows are applied. Following this another chunk is copied, and so

unsharded to an unsharded keyspace using a different vindex than the source keyspace. • Materialized Views: You can specify a materialization rule that creates a view of the source table into a target keyspace For example, it can be used to control the cut-over during resharding. In the case of materialized views, it can be used to establish equivalence of tables, which will allow VTGate to compute the most optimal chunks. After each chunk is copied, replication is resumed until it’s caught up. VReplication ensures that only changes that affect existing rows are applied. Following this another chunk is copied, and so

rec.Error() } return keyspaces, nil } In the first chunk of highlighted code, rec records an error of a single keyspace. In the second chunk of highlighted code, GetKeySpaces return nil and the error

orders where in_keyrange( mname, ‘unicode_loose_md5’, ‘-80’) 46 VITESS.IO Materializ ed Views Use Cases Real- Time Rollups Reshardi ng Backfilling of Lookup vindexes Schema deploym ent