Details
-
Task
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
-
None
Description
When using remote table engines, like FEDERATEDX or CONNECT, usually one wouldn't want to have master side changes to be replicated to slaves, as these would just lead to duplicate actions on the remote tables by default.
In edge cases though, where e.g. CONNECTION parameters for CONNECT tables on the slave side have been altered to point to different servers than on the master, replication for such tables may actually be wanted though.
Right now this could only be solved by using replicate_do/ignore_table rules, and having a consistent table naming scheme that would allow for CONNECT tables to be easily identified, or by adding per-table rules one by one.
So I'd request to be able to outright ignore CONNECT or FEDERATEDX tables by default, by having a new filter like
replicate_ignore_engine=CONNECT,FEDERATEDX
This would obviously be a ROW-only filter.
Attachments
Issue Links
- relates to
-
MDEV-19964 S3 replication support
- Closed