Overview of the Issue
On a shard by shard migration, when you start a MoveTables for Sequence tables it can drop the sequence attribute from the vSchema.
Reproduction Steps
- Apply your VSchema for sequences and validate:
$ vtctlclient --server localhost:15999 GetVSchema fane_import
{
"tables": {
"sbtest1_seq": {
"type": "sequence"
},
"sbtest2_seq": {
"type": "sequence"
},
"sbtest3_seq": {
"type": "sequence"
},
"sbtest4_seq": {
"type": "sequence"
},
"sbtest5_seq": {
"type": "sequence"
},
"sbtest6_seq": {
"type": "sequence"
}
}
}
- Start your MoveTables command (this is using shard by shard migration)
$ vtctlclient --server localhost:15999 MoveTables -- --cells="${CELLS}" --all --tablet_types="in_order:REPLICA,PRIMARY" --source="fane_import_source" Create fane_import.import
Waiting for workflow to start:
Workflow started successfully with 1 stream(s)
The following vreplication streams exist for workflow fane_import.import:
id=2 on -/aws_useast1b_4-4141702636: Status: Copying. VStream Lag: 0s.
- Check you vSchema once again, and note the sequences attribute has been removed:
$ vtctlclient --server localhost:15999 GetVSchema fane_import
{
"tables": {
"sbtest1_seq": {},
"sbtest2_seq": {},
"sbtest3_seq": {},
"sbtest4_seq": {},
"sbtest5_seq": {},
"sbtest6_seq": {}
}
}
Binary Version
Operating System and Environment details
Log Fragments
Overview of the Issue
On a shard by shard migration, when you start a MoveTables for Sequence tables it can drop the sequence attribute from the vSchema.
Reproduction Steps
Binary Version
Operating System and Environment details
Log Fragments