The Vitess 5.0 DocumentationYou requested that the schema for customer and corder be copied to customer using the copySchema directive. The move in the VSchema should not make a difference yet because any queries sent to customer Shard 0 was already there. We have now added shards -80 and 80-. We’ve also added the copySchema directive which requests that the schema from shard 0 be copied into the new shards. Shard naming What is Shard 0 was already there. We have now added shards -80 and 80-. We’ve also added the CopySchema directive which requests that the schema from shard 0 be copied into the new shards. Shard naming What is0 码力 | 206 页 | 875.06 KB | 1 年前3
The Vitess 6.0 DocumentationShard 0 was already there. We have now added shards -80 and 80-. We’ve also added the CopySchema directive which requests that the schema from shard 0 be copied into the new shards. Shard naming What is customer/0 zone1 -200 Note: This change does not change the actual routing yet. We will use a switch directive to achieve that shortly. Start the Move In this step we will initiate the MoveTables, which copies You requested that the schema for customer and corder be copied to customer using the copySchema directive. 204 The move in the VSchema should not make a difference yet because any queries sent to customer0 码力 | 210 页 | 846.79 KB | 1 年前3
The Vitess 7.0 DocumentationShard 0 was already there. We have now added shards -80 and 80-. We’ve also added the CopySchema directive which requests that the schema from shard 0 be copied into the new shards. Shard naming What is customer/0 zone1 -200 Note: This change does not change the actual routing yet. We will use a switch directive to achieve that shortly. Start the Move In this step we will initiate the MoveTables, which copies You requested that the schema for customer and corder be copied to customer using the copySchema directive. The move in the VSchema should not make a difference yet because any queries sent to customer0 码力 | 254 页 | 949.63 KB | 1 年前3
The Vitess 8.0 DocumentationHowever, the original underlying database could also have been using an -init_db_name_override directive of its own, and this value should then be set to match that. - -init_shard 0 - here 0 is the shard Shard 0 was already there. We have now added shards -80 and 80-. We’ve also added the CopySchema directive which requests that the schema from shard 0 be copied into the new shards. Shard naming What is You requested that the schema for customer and corder be copied to customer using the copySchema directive. The move in the VSchema should not make a difference yet because any queries sent to customer0 码力 | 331 页 | 1.35 MB | 1 年前3
The Vitess 9.0 DocumentationHowever, the original underlying database could also have been using an -init_db_name_override directive of its own, and this value should then be set to match that. - -init_shard 0 - here 0 is the shard Shard 0 was already there. We have now added shards -80 and 80-. We’ve also added the CopySchema directive which requests that the schema from shard 0 be copied into the new shards. Shard naming What is You requested that the schema for customer and corder be copied to customer using the copySchema directive. The move in the VSchema should not make a difference yet because any queries sent to customer0 码力 | 417 页 | 2.96 MB | 1 年前3
The Vitess 11.0 DocumentationHowever, the original underlying database could also have been using an -init_db_name_override directive of its own, and this value should then be set to match that. • -init_shard 0 - here 0 is the shard Shard 0 was already there. We have now added shards -80 and 80-. We’ve also added the CopySchema directive which requests that the schema from shard 0 be copied into the new shards. Shard naming What is You requested that the schema for customer and corder be copied to customer using the copySchema directive. The move in the VSchema should not make a difference yet because any queries sent to customer0 码力 | 481 页 | 3.14 MB | 1 年前3
The Vitess 10.0 Documentation
However, the original underlying database could also have been using an -init_db_name_override directive of its own, and this value should then be set to match that. - -init_shard 0 - here 0 is the shard Shard 0 was already there. We have now added shards -80 and 80-. We’ve also added the CopySchema directive which requests that the schema from shard 0 be copied into the new shards. Shard naming What is You requested that the schema for customer and corder be copied to customer using the copySchema directive. The move in the VSchema should not make a difference yet because any queries sent to customer0 码力 | 455 页 | 3.07 MB | 1 年前3
The Vitess 12.0 DocumentationHowever, the original underlying database could also have been using an -init_db_name_override directive of its own, and this value should then be set to match that. • -init_shard 0 - here 0 is the shard Shard 0 was already there. We have now added shards -80 and 80-. We’ve also added the CopySchema directive which requests that the schema from shard 0 be copied into the new shards. Shard naming What is You requested that the schema for customer and corder be copied to customer using the copySchema directive. The move in the VSchema should not make a difference yet because any queries sent to customer0 码力 | 534 页 | 3.32 MB | 1 年前3
共 8 条
- 1













