Replication and Binary Logging Options and Variables Filtering Rules” . You can also create such a filter by issuing a  CHANGE REPLICATION FILTER REPLICATE_WILD_DO_TABLE  statement. This option supports channel specific replication filters, enabling multi-source replicas to use specific filters for different sources. To configure a channel specific replication filter on a channel named channel_1  use  --replicate-wild-do-table: channel_1 : db_name.tbl_name . In this case, the first colon is interpreted as a separator and subsequent colons are literal colons. See Section 17.2.5.4, “Replication Channel Based Filters”  for more information. Note Global replication filters cannot be used on a MySQL server instance that is configured for Group Replication, because filtering transactions on some servers would make the group unable to reach agreement on a consistent state. Channel specific replication filters can be used on replication channels that are not directly involved with Group Replication, such as where a group member also acts as a replica to a source that is outside the group. They cannot be used on the  group_replication_applier  or  group_replication_recovery channels. This option applies to tables, views, and triggers. It does not apply to stored procedures and functions, or events. To filter statements operating on the latter objects, use one or more of the  --replicate-*-db options. As an example,  --replicate-wild-do-table=foo%.bar%  replicates only updates that use a table where the database name starts with  foo  and the table name starts with  bar . If the table name pattern is  % , it matches any table name and the option also applies to database-level statements ( CREATE DATABASE ,  DROP DATABASE , and  ALTER DATABASE ). For example, if you use --replicate-wild-do-table=foo%.% , database-level statements are replicated if the database name matches the pattern  foo% . To include literal wildcard characters in the database or table name patterns, escape them with a backslash. For example, to replicate all tables of a database that is named  my_own%db , but not replicate tables from the  my1ownAABCdb  database, you should escape the  _  and  %  characters like this:  -- replicate-wild-do-table=my\_own\%db . If you use the option on the command line, you might need to double the backslashes or quote the option value, depending on your command interpreter. For example, with the  bash  shell, you would need to type  --replicate-wild-do-table=my\\_own\\ %db . • --replicate-wild-ignore-table= db_name.tbl_name Command-Line Format --replicate-wild-ignore-table=name Type String Creates a replication filter which keeps the replication SQL thread from replicating a statement in which any table matches the given wildcard pattern. To specify more than one table to ignore, use this option multiple times, once for each table. This works for cross-database updates. See Section 17.2.5, “How Servers Evaluate Replication Filtering Rules” . You can also create such a filter by issuing a  CHANGE REPLICATION FILTER REPLICATE_WILD_IGNORE_TABLE  statement. This option supports channel specific replication filters, enabling multi-source replicas to use specific filters for different sources. To configure a channel specific replication filter on a channel named channel_1  use  --replicate-wild-ignore: channel_1 : db_name.tbl_name . In this case, the 3514