[MDEV-26706] Enable per table gtid domain_id Created: 2021-09-28  Updated: 2021-09-28

Status: Open
Project: MariaDB Server
Component/s: Replication
Fix Version/s: None

Type: Task Priority: Major
Reporter: VAROQUI Stephane Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-6901 [PATCH] session.gtid_domain_id should... Stalled
relates to MDEV-4831 Replication to store filter in master... Open
relates to MDEV-26632 multi source replication filters brea... Closed

 Description   

Replication filters have many issues and domain filtering works better to allow selective filtering on replicas such task would attach one or many domain per table definition enabling user define logical dataset to be filtered or apply on a replica. Today using extra domain is.an application layer task and is out of the scope of sysops dbops making such good feature a no go in most case.



 Comments   
Comment by Daniel Black [ 2021-09-28 ]

This will get tricky if two table updates are in the same transaction. Which gtid will it get?

Comment by VAROQUI Stephane [ 2021-09-28 ]

Yep in row based no issue but in statement could just works as in filters today so if stmt cross multi domains tables , all domains has to be store in binlog so that filetring can works as described today
If the filter take place on master anyway on the request of a replica for saving bandwidth this does not need extra binlog domain information , if taking place on the slave the per table domain information can be found in table definition

Comment by VAROQUI Stephane [ 2021-09-28 ]

For resolving the selective purge on master and store on replica a syntax ALTER TABLE ADD DOMAIN x FOR ALL|DELETE|UPDATE|REPLACE|INSERT can be introduce

Generated at Thu Feb 08 09:47:20 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.