Feature Description

Feature Description

Building somewhat on the momentum created by #13685, some (e.g. @lizztheblizz) have requested a feature or flag for the MoveTables Create subcommand that automatically strips the MySQL auto_increment column definitions from tables that are being moved into a sharded target keyspace.

As of today, the only way to do so is to manually establish the full target schema up front, OR by manually altering the tables after the workflow has already started, but before switching traffic. The latter can be an extremely expensive operation if the table is very large and must be rebuilt and thus we should avoid it whenever possible, as it would also cause the VReplication workflow to lag.

Since auto_increment is never supported on sharded keyspaces either way, it feels reasonable to default to stripping auto_increment definitions on workflows where the target keyspace is sharded.

Use Case(s)

Any situation when we are using MoveTables to import data from an unsharded keyspace into a sharded keyspace. i.e. the same use cases as referenced in #13685.