You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since #15679 we automatically strip any MySQL auto_increment clauses on tables that are being moved (using the MoveTables command) from an unsharded keyspace to a sharded one. And since #13656 we support initializing any sequences in the target keyspace on SwitchTraffic.
It would be really nice if we also supported automatically replacing those MySQL auto_increment clauses with Vitess sequences. This would eliminate a fair amount of toil and potential for mistakes.
Use Case(s)
Moving tables from an unsharded to a sharded keyspace, which is common e.g. when initialing migrating into Vitess. And one initial hurdle is moving from MySQL managed auto_increment values in the MySQL schema to Vitess managed AutoIncrement values in the Vitess vschema.
The text was updated successfully, but these errors were encountered:
Feature Description
Since #15679 we automatically strip any MySQL
auto_increment
clauses on tables that are being moved (using theMoveTables
command) from an unsharded keyspace to a sharded one. And since #13656 we support initializing any sequences in the target keyspace onSwitchTraffic
.It would be really nice if we also supported automatically replacing those MySQL auto_increment clauses with Vitess sequences. This would eliminate a fair amount of toil and potential for mistakes.
Use Case(s)
Moving tables from an unsharded to a sharded keyspace, which is common e.g. when initialing migrating into Vitess. And one initial hurdle is moving from MySQL managed auto_increment values in the MySQL schema to Vitess managed AutoIncrement values in the Vitess vschema.
The text was updated successfully, but these errors were encountered: