com/vitessio/vitess/pull/12939 ● https://github.com/vitessio/vitess/pull/12940 Vitess uses Go templating a number of places to generate HTML but does not escape the parameters to the template. Vitess was not possible. To guard against future issues with templating, Vitess now uses the https://github.com/google/safehtml library for html templating. In addition, Vitess now uses templates instead of raw

VitessAware big_tables NoOp bulk_insert_buffer_size NoOp debug NoOp default_storage_engine NoOp default_tmp_storage_engine NoOp innodb_strict_mode NoOp innodb_support_xa NoOp innodb_table_locks NoOp innodb_tmpdir via warning that settings are either ignored or modification was not allowed. E.g. default_storage_engine, debug, etc. Vitess Aware These are the system variables for which Vitess needs to change behavior etc. Reserve connection These are the system variables that Vitess will send down to the storage engine and modify the settings at the session connection level. E.g. sql_mode, sql_safe_updates, etc. This

VitessAware big_tables NoOp bulk_insert_buffer_size NoOp debug NoOp default_storage_engine NoOp default_tmp_storage_engine NoOp innodb_strict_mode NoOp innodb_support_xa NoOp innodb_table_locks NoOp innodb_tmpdir via warning that settings are either ignored or modification was not allowed. E.g. default_storage_engine, debug, etc. Vitess Aware These are the system variables for which Vitess needs to change behavior etc. Reserve connection These are the system variables that Vitess will send down to the storage engine and modify the settings at the session connection level. E.g. sql_mode, sql_safe_updates, etc. This

VitessAware big_tables NoOp bulk_insert_buffer_size NoOp debug NoOp default_storage_engine NoOp default_tmp_storage_engine NoOp innodb_strict_mode NoOp innodb_support_xa NoOp innodb_table_locks NoOp innodb_tmpdir tablet • Possibly auto-retries migrations The executor also receives requests from the tablet’s query engine/executor to: • Submit a new migration • Cancel a migration • Retry a migration It also responds via warning that settings are either ignored or modification was not allowed. E.g. default_storage_engine, debug, etc. Vitess Aware These are the system variables for which Vitess needs to change behavior

VitessAware big_tables NoOp bulk_insert_buffer_size NoOp debug NoOp default_storage_engine NoOp default_tmp_storage_engine NoOp innodb_strict_mode NoOp innodb_support_xa NoOp innodb_table_locks NoOp innodb_tmpdir via warning that settings are either ignored or modification was not allowed. E.g. default_storage_engine, debug, etc. Vitess Aware These are the system variables for which Vitess needs to change behavior etc. Reserve connection These are the system variables that Vitess will send down to the storage engine and modify the settings at the session connection level. E.g. sql_mode, sql_safe_updates, etc. This

we get started, let’s get a few things out of the way: 1. Install Minikube and start a Minikube engine: minikube start 2. Install kubectl and ensure it is in your PATH. For example, on Linux: curl we get started, let’s get a few things out of the way: 1. Install Minikube and start a Minikube engine. We recommend using Kubernetes 1.14, as this is a common denom- inator across public clouds: bash check for receivers: To be added. • Monitoring support: To be added. • Dropped tables: The message engine does not currently detect dropped tables. Known limitations The message feature is currently in

VitessAware big_tables NoOp bulk_insert_buffer_size NoOp debug NoOp default_storage_engine NoOp default_tmp_storage_engine NoOp innodb_strict_mode NoOp innodb_support_xa NoOp innodb_table_locks NoOp innodb_tmpdir we get started, let’s get a few things out of the way: 1. Install Minikube and start a Minikube engine: minikube start 2. Install kubectl and ensure it is in your PATH. For example, on Linux: curl we get started, let’s get a few things out of the way: 1. Install Minikube and start a Minikube engine. We recommend using Kubernetes 1.14, as this is a common denom- inator across public clouds: bash

we get started, let’s get a few things out of the way: 1. Install Minikube and start a Minikube engine: minikube start --cpus=4 --memory=8000 Note the additional resource requirements. In order to go check for receivers: To be added. • Monitoring support: To be added. • Dropped tables: The message engine does not currently detect dropped tables. Known limitations The message feature is currently in timely delivery instead of waiting for the next polling cycle. • Changed properties: Although the engine detects new message tables, it does not refresh properties of an existing table. • A SELECT style

Before we get started, let’s get a few things out of the way: 1. Install Minikube Start a Minikube engine: minikube start --kubernetes-version v1.15.0 --cpus=4 --memory=5000. Note the additional resource check for receivers: To be added. • Monitoring support: To be added. • Dropped tables: The message engine does not currently detect dropped tables. Known limitations The message feature is currently in timely delivery instead of waiting for the next polling cycle. • Changed properties: Although the engine detects new message tables, it does not refresh properties of an existing table. • A SELECT style

Slack Members 1000 + Forks 8,000 + Stars 4 Key Adopters YouTube in 2010 2013 Storage Engine running as Stateless Application Stateless Storage 8 VITESS.IO 2015 9 VITESS.IO Oldest, since