Flexible routing for Vitess and MongoDB
Vitess tables support per-table keyspaces and custom primary keys, and MongoDB collections can target their own Transfer topic configuration.
Vitess tables can now use per-table keyspaces and custom primary keys, with progress tracked independently for each keyspace. MongoDB collections can also target their own Transfer topic configuration, enabling collection-specific routing and transform settings.
Why this matters
- Replicate Vitess tables across multiple keyspaces from one pipeline
- Set an explicit primary key for tables that need one
- Apply distinct topic-level behavior to individual MongoDB collections