needs. However, OLAP mode has no limit to the number of rows returned. In order to change to this mode, you may issue the following command before executing your query: set workload='olap' You can also and reparent commands. The general convention is to send OLTP queries to REPLICA tablet types, and OLAP queries to RDONLY. Is there a list of supported/unsupported queries? Please see “SQL Syntax” under slightly stale data, the queries should be sent to REPLICA tablets for OLTP, and RDONLY tablets for OLAP workloads. This allows you to scale your read traffic more easily, and gives you the ability to distribute

needs. However, OLAP mode has no limit to the number of rows returned. In order to change to this mode, you may issue the following command before executing your query: set workload='olap' 23 You can and reparent commands. The general convention is to send OLTP queries to REPLICA tablet types, and OLAP queries to RDONLY. Is there a list of supported/unsupported queries? Please see “SQL Syntax” under slightly stale data, the queries should be sent to REPLICA tablets for OLTP, and RDONLY tablets for OLAP workloads. This allows you to scale your read traffic more easily, and gives you the ability to distribute

needs. However, OLAP mode has no limit to the number of rows returned. In order to change to this mode, you may issue the following command before executing your query: set workload='olap' You can also and reparent commands. The general convention is to send OLTP queries to REPLICA tablet types, and OLAP queries to RDONLY. Is there a list of supported/unsupported queries? Please see “SQL Syntax” under slightly stale data, the queries should be sent to REPLICA tablets for OLTP, and RDONLY tablets for OLAP workloads. This allows you to scale your read traffic more easily, and gives you the ability to distribute

needs. However, OLAP mode has no limit to the number of rows returned. In order to change to this mode, you may issue the following command before executing your query: set workload='olap' You can also and reparent commands. The general convention is to send OLTP queries to REPLICA tablet types, and OLAP queries to RDONLY. Is there a list of supported/unsupported queries? Please see “SQL Syntax” under slightly stale data, the queries should be sent to REPLICA tablets for OLTP, and RDONLY tablets for OLAP workloads. This allows you to scale your read traffic more easily, and gives you the ability to distribute

• Not end with a period 39 Consists of five parts: • Category – VTGate / MySQL compatibility – OLAP – System – VReplication – VTtablet – VTorc – PITR – Examples – Docs – Build – Other • Label – BugFix slightly stale data, the queries should be sent to REPLICA tablets for OLTP, and RDONLY tablets for OLAP workloads. This allows you to scale your read traffic more easily, and gives you the ability to distribute really well. • Not all cells need rdonly (or batch) instances. Only the cells that run batch jobs, or OLAP jobs, really need them. Note Vitess uses local-cell data first, and is very resilient to any cell

slightly stale data, the queries should be sent to REPLICA tablets for OLTP, and RDONLY tablets for OLAP workloads. This allows you to scale your read traffic more easily, and gives you the ability to distribute really well. • Not all cells need rdonly (or batch) instances. Only the cells that run batch jobs, or OLAP jobs, really need them. Note Vitess uses local-cell data first, and is very resilient to any cell recommended to design the VSchema in such a way that cross- shard modifications are not required. OLAP Workload By default, Vitess sets some intentional restrictions on the execution time and number of

• Not end with a period 40 Consists of five parts: • Category – VTGate / MySQL compatibility – OLAP – System – VReplication – VTtablet – VTorc – PITR – Examples – Docs – Build – Other • Label – BugFix slightly stale data, the queries should be sent to REPLICA tablets for OLTP, and RDONLY tablets for OLAP workloads. This allows you to scale your read traffic more easily, and gives you the ability to distribute really well. • Not all cells need rdonly (or batch) instances. Only the cells that run batch jobs, or OLAP jobs, really need them. Note Vitess uses local-cell data first, and is very resilient to any cell

slightly stale data, the queries should be sent to REPLICA tablets for OLTP, and RDONLY tablets for OLAP workloads. This allows you to scale your read traffic more easily, and gives you the ability to distribute really well. • Not all cells need rdonly (or batch) instances. Only the cells that run batch jobs, or OLAP jobs, really need them. Note Vitess uses local-cell data first, and is very resilient to any cell recommended to design the VSchema in such a way that cross- shard modifications are not required. OLAP Workload By default, Vitess sets some intentional restrictions on the execution time and number of