Morgan Tocker
Morgan Tocker
### Feature Description There is a previous FR for this here: https://github.com/vitessio/vitess/issues/3259 I made partial progress in https://github.com/vitessio/vitess/pull/5808, but the work was not complete. I have a branch for this...
## A Pull Request should be associated with an Issue. > We wish to have discussions in Issues. A single issue may be targeted by multiple PRs. > If you're...
Currently MoveTables logically copies data from one database schema to another. However, we have the use case that we want to copy from one source to N destinations based on...
MoveTables uses buffered copies with require `binlog_row_image = FULL`. We check for this in migrations, but not in moves. There needs to be some way of preventing running if it...
In movetables there are advantages to defer rebuilding secondary index creation, since MySQL can do this without redo logging and in an optimized way. It has to be optional though,...
It will work slightly different to regular table notification because we technically have to discover any new tables, not just the ones we are copying.
Currently spirit will always resume from checkpoint if it is possible. We have seen some cases where a change is stopped for several days, then picked up again, and replaying...
Currently spirit works like this: - It starts a replication client to subscribe to table changes (tracking the PK only). - It then progressively copies from the table using `INSERT...
Forked from https://github.com/block/spirit/issues/472 In https://github.com/block/spirit/pull/478 I suggest we go with other solutions first, but this is a reasonable stategy, and so we can track it here and come back to...