Details
-
New Feature
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
-
MXS-CAPACITY-Q4-2026
Description
Problem
odbc_include_tables can only be changed by editing the configuration and restarting MaxScale, which interrupts CDC replication for all tables as well as stopping all connections and more that maxscale is managing.
Goal
Allow odbc_include_tables to be altered while MaxScale is running (e.g. via maxctrl alter), without interrupting replication of unaffected tables.
Requirements
- A table added to the list starts replicating from the current GTID
- A table removed from the list stops replicating at a GTID boundary; target data is left untouched.
- The change is atomic: if it fails, the previous list stays active.
- The new value is persisted, survives restart, and propagates through config sync.
- The effective GTID and config change is logged for audit purpose
- (probably its own ticket?) a bulk copy argument added to online copy the new table being added and then immediately start CDC for that table so that its up to date easily
2. Acceptance criteria
- Adding a table at runtime leaves the target with exactly the source rows from the effective starting GTID, while other tables keep replicating.
- Removing a table stops its replication at a defined GTID (logged) and leaves its target data in place.
- After restart, the list reflects the runtime change.