content_image/776469.jpg content_image/776471.jpg content_image/776476.jpg
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. 

<img src='content_image/776469.jpg'>

## 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. 

As an example, --replicate-wild-ignore-table=foo%.bar%  does not replicate updates that use a table where the database name starts with foo  and the table name starts with bar . For information about how matching works, see the description of the --replicate-wild-do-table option. The rules for including literal wildcard characters in the option value are the same as for -- replicate-wild-ignore-table  as well. 

• --skip-slave-start 

<img src='content_image/776471.jpg'>

Tells the replica server not to start the replication I/O and SQL threads when the server starts. To start the threads later, use a START REPLICA | SLAVE  statement. 

From MySQL 8.0.24, you can use the skip_slave_start  system variable in place of the command line option to allow access to this feature using MySQL Server’s privilege structure, so that database administrators do not need any privileged access to the operating system. 

• --slave-skip-errors=[ err_code1 , err_code2 ,...|all|ddl_exist_errors] 

<img src='content_image/776476.jpg'>

