. . . . . 113 Point In Time Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Point in Time Recovery . . . . . . . . . . . . . . subset of the SQL language. Vitess is not a simple key-value store. It supports complex query semantics such as where clauses, JOINS, aggregation functions, and more. NoSQL datastores do not usually support issues where Vitess differs from MySQL. 99 Transaction Model Vitess provides READ COMMITTED semantics when executing cross-shard queries. This differs to MySQL, which defaults to REPEATABLE READ. SQL

. . . . . 93 Point In Time Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Point in Time Recovery . . . . . . . . . . . . . . . subset of the SQL language. Vitess is not a simple key-value store. It supports complex query semantics such as where clauses, JOINS, aggregation functions, and more. NoSQL datastores do not usually support compatibility issues where Vitess differs from MySQL. Transaction Model Vitess provides READ COMMITTED semantics when executing cross-shard queries. This differs to MySQL, which defaults to REPEATABLE READ. SQL

. . . . . 103 Point In Time Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Point in Time Recovery . . . . . . . . . . . . . . subset of the SQL language. Vitess is not a simple key-value store. It supports complex query semantics such as where clauses, JOINS, aggregation functions, and more. NoSQL datastores do not usually support compatibility issues where Vitess differs from MySQL. Transaction Model Vitess provides READ COMMITTED semantics when executing cross-shard queries. This differs to MySQL, which defaults to REPEATABLE READ. SQL

subset of the SQL language. Vitess is not a simple key-value store. It supports complex query semantics such as where clauses, JOINS, aggregation functions, and more. NoSQL datastores do not usually support compatibility issues where Vitess differs from MySQL. Transaction Model Vitess provides READ COMMITTED semantics when executing cross-shard queries. This differs to MySQL, which defaults to REPEATABLE READ. SQL local only to each shard. Vitess Sequences are provided as an alternative, which have very close semantics to auto_increment. USE Statements Vitess allows you to select a keyspace using the MySQL USE statement

subset of the SQL language. Vitess is not a simple key-value store. It supports complex query semantics such as where clauses, JOINS, aggregation functions, and more. NoSQL datastores do not usually support issues where Vitess differs from MySQL. 43 Transaction Model Vitess provides READ COMMITTED semantics when executing cross-shard queries. This differs to MySQL, which defaults to REPEATABLE READ. SQL local only to each shard. Vitess Sequences are provided as an alternative, which have very close semantics to auto_increment. Extensions to MySQL Syntax SHOW Statements Vitess supports a few additional

subset of the SQL language. Vitess is not a simple key-value store. It supports complex query semantics such as where clauses, JOINS, aggregation functions, and more. NoSQL datastores do not usually support compatibility issues where Vitess differs from MySQL. Transaction Model Vitess provides READ COMMITTED semantics when executing cross-shard queries. This differs to MySQL, which defaults to REPEATABLE READ. SQL local only to each shard. Vitess Sequences are provided as an alternative, which have very close semantics to auto_increment. Extensions to MySQL Syntax SHOW Statements Vitess supports a few additional

. . . . . 62 Point In Time Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Point in Time Recovery . . . . . . . . . . . . . . . subset of the SQL language. Vitess is not a simple key-value store. It supports complex query semantics such as where clauses, JOINS, aggregation functions, and more. NoSQL datastores do not usually support Time Recovery Point in Time Recovery Supported Databases • MySQL 5.7 #### Believed to work, but untested • MySQL 8.0 Introduction The Point in Time Recovery feature in Vitess enables recovery of data

subset of the SQL language. Vitess is not a simple key-value store. It supports complex query semantics such as where clauses, JOINS, aggregation functions, and more. NoSQL datastores do not usually support Topology Service is only used to get the topology information at startup and in the background. 56 Recovery If a Local Topology Service dies and is not recoverable, it can be wiped out. All the tablets in compatibility issues where Vitess differs from MySQL. Transaction Model Vitess provides READ COMMITTED semantics when executing cross-shard queries. This differs to MySQL, which defaults to REPEATABLE READ. SQL