The Vitess 5.0 Documentationconsiderations: • What are the highest QPS queries, and what are the where clauses for them? • Cardinality of the column; it must be high. • Do we want some rows to live together to support in-shard joins clause uses customer_id. So, it shall have a Primary Vindex. • Given that it has lots of users, its cardinality is also high. • For the corder table, we have a choice between customer_id and order_id. Given map to a tenant_id. In such cases, the cardinality of a tenant id may be too low. It’s also common that such systems have queries that use other high cardinality columns in their where clauses. Those should0 码力 | 206 页 | 875.06 KB | 1 年前3- The Vitess 6.0 Documentationconsiderations: • What are the highest QPS queries, and what are the where clauses for them? • Cardinality of the column; it must be high. • Do we want some rows to live together to support in-shard joins clause uses customer_id. So, it shall have a Primary Vindex. • Given that it has lots of users, its cardinality is also high. • For the corder table, we have a choice between customer_id and order_id. Given map to a tenant_id. In such cases, the cardinality of a tenant id may be too low. It’s also common that such systems have queries that use other high cardinality columns in their where clauses. Those should0 码力 | 210 页 | 846.79 KB | 1 年前3
- The Vitess 7.0 Documentationconsiderations: • What are the highest QPS queries, and what are the where clauses for them? • Cardinality of the column; it must be high. • Do we want some rows to live together to support in-shard joins clause uses customer_id. So, it shall have a Primary Vindex. • Given that it has lots of users, its cardinality is also high. • For the corder table, we have a choice between customer_id and order_id. Given map to a tenant_id. In such cases, the cardinality of a tenant id may be too low. It’s also common that such systems have queries that use other high cardinality columns in their where clauses. Those should0 码力 | 254 页 | 949.63 KB | 1 年前3
- The Vitess 8.0 Documentationconsiderations: • What are the highest QPS queries, and what are the WHERE clauses for them? 254 • Cardinality of the column; it must be high. • Do we want some rows to live together to support in-shard joins clause uses customer_id. So, it shall have a Primary Vindex. • Given that it has lots of users, its cardinality is also high. • For the corder table, we have a choice between customer_id and order_id. Given considerations: • What are the highest QPS queries, and what are the where clauses for them? • Cardinality of the column; it must be high. • Do we want some rows to live together to support in-shard joins0 码力 | 331 页 | 1.35 MB | 1 年前3
- The Vitess 9.0 Documentationconsiderations: • What are the highest QPS queries, and what are the WHERE clauses for them? • Cardinality of the column; it must be high. • Do we want some rows to live together to support in-shard joins clause uses customer_id. So, it shall have a Primary Vindex. • Given that it has lots of users, its cardinality is also high. 294 • For the corder table, we have a choice between customer_id and order_id. considerations: • What are the highest QPS queries, and what are the where clauses for them? • Cardinality of the column; it must be high. • Do we want some rows to live together to support in-shard joins0 码力 | 417 页 | 2.96 MB | 1 年前3
- The Vitess 11.0 Documentationconsiderations: • What are the highest QPS queries, and what are the WHERE clauses for them? • Cardinality of the column; it must be high. • Do we want some rows to live together to support in-shard joins clause uses customer_id. So, it shall have a Primary Vindex. • Given that it has lots of users, its cardinality is also high. • For the corder table, we have a choice between customer_id and order_id. Given considerations: • What are the highest QPS queries, and what are the where clauses for them? • Cardinality of the column; it must be high. • Do we want some rows to live together to support in-shard joins0 码力 | 481 页 | 3.14 MB | 1 年前3
- The Vitess 10.0 Documentation
considerations: • What are the highest QPS queries, and what are the WHERE clauses for them? • Cardinality of the column; it must be high. • Do we want some rows to live together to support in-shard joins clause uses customer_id. So, it shall have a Primary Vindex. • Given that it has lots of users, its cardinality is also high. • For the corder table, we have a choice between customer_id and order_id. Given considerations: • What are the highest QPS queries, and what are the where clauses for them? • Cardinality of the column; it must be high. • Do we want some rows to live together to support in-shard joins0 码力 | 455 页 | 3.07 MB | 1 年前3
- The Vitess 12.0 Documentationconsiderations: • What are the highest QPS queries, and what are the WHERE clauses for them? • Cardinality of the column; it must be high. • Do we want some rows to live together to support in-shard joins clause uses customer_id. So, it shall have a Primary Vindex. • Given that it has lots of users, its cardinality is also high. 359 • For the corder table, we have a choice between customer_id and order_id. considerations: • What are the highest QPS queries, and what are the where clauses for them? • Cardinality of the column; it must be high. • Do we want some rows to live together to support in-shard joins0 码力 | 534 页 | 3.32 MB | 1 年前3
共 8 条
- 1