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
-
Activity
Field | Original Value | New Value |
---|---|---|
Link |
This issue relates to |
Link | This issue relates to MENT-906 [ MENT-906 ] |
Assignee | Ralf Gebhardt [ ralf.gebhardt@mariadb.com ] |
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 ont he 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. |
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. |
Workflow | MariaDB v3 [ 107528 ] | MariaDB v4 [ 131268 ] |
Link | This issue is duplicated by MENT-1001 [ MENT-1001 ] |
Status | Open [ 1 ] | Needs Feedback [ 10501 ] |
Comment | [ A comment with security level 'Developers' was removed. ] |
Status | Needs Feedback [ 10501 ] | Open [ 1 ] |
Summary | Feature request: replicate_do/ignore_engine | Feature request: replicate_do_engine/replicate_ignore_engine |
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. |
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. |
Status | Open [ 1 ] | Needs Feedback [ 10501 ] |
Status | Needs Feedback [ 10501 ] | Open [ 1 ] |
Assignee | Ralf Gebhardt [ ralf.gebhardt@mariadb.com ] |
Zendesk Related Tickets | 147062 146234 |
Zendesk Related Tickets | 146234 147062 | 146234 147062 203525 |
Zendesk active tickets | 203525 |
Zendesk active tickets | 203525 |
DDL for CONNECT, FEDERATED and the likes should still be replicated, only DML needs to be filtered indeed as that is already replicated otherwise.
So my request indeed looks similar to s3_slave_ignore_updates, just in a more general form that handles this on the server level for all potentially affected engines.