The Vitess 9.0 Documentationthis table with an unsharded table will be treated as a local join. Typically, such a table has a canonical source in an unsharded keyspace, and the copies in the sharded keyspace are kept up-to-date through they are not necessary because these are implicitly created as you bring up the vttablets. The canonical information for keyspaces and shards is initially created in the global topo. This information is0 码力 | 417 页 | 2.96 MB | 1 年前3- The Vitess 11.0 Documentationthis table with an unsharded table will be treated as a local join. Typically, such a table has a canonical source in an unsharded keyspace, and the copies in the sharded keyspace are kept up-to-date through they are not necessary because these are implicitly created as you bring up the vttablets. The canonical information for keyspaces and shards is initially created in the global topo. This information is0 码力 | 481 页 | 3.14 MB | 1 年前3
- The Vitess 10.0 Documentation
this table with an unsharded table will be treated as a local join. Typically, such a table has a canonical source in an unsharded keyspace, and the copies in the sharded keyspace are kept up-to-date through they are not necessary because these are implicitly created as you bring up the vttablets. The canonical information for keyspaces and shards is initially created in the global topo. This information is0 码力 | 455 页 | 3.07 MB | 1 年前3
- The Vitess 6.0 Documentationthis table with an unsharded table will be treated as a local join. Typically, such a table has a canonical source in an unsharded keyspace, and the copies in the sharded keyspace are kept up-to-date through0 码力 | 210 页 | 846.79 KB | 1 年前3
- The Vitess 5.0 Documentationthis table with an unsharded table will be treated as a local join. Typically, such a table has a canonical source in an unsharded keyspace, and the copies in the sharded keyspace are kept up-to-date through0 码力 | 206 页 | 875.06 KB | 1 年前3
- The Vitess 7.0 Documentationthis table with an unsharded table will be treated as a local join. Typically, such a table has a canonical source in an unsharded keyspace, and the copies in the sharded keyspace are kept up-to-date through0 码力 | 254 页 | 949.63 KB | 1 年前3
- The Vitess 12.0 Documentationthis table with an unsharded table will be treated as a local join. Typically, such a table has a canonical source in an unsharded keyspace, and the copies in the sharded keyspace are kept up-to-date through they are not necessary because these are implicitly created as you bring up the vttablets. The canonical information for keyspaces and shards is initially created in the global topo. This information is0 码力 | 534 页 | 3.32 MB | 1 年前3
- The Vitess 8.0 Documentationthis table with an unsharded table will be treated as a local join. Typically, such a table has a canonical source in an unsharded keyspace, and the copies in the sharded keyspace are kept up-to-date through0 码力 | 331 页 | 1.35 MB | 1 年前3
共 8 条
- 1