EC
1703
MySQLWARNINGNotableReplicationHIGH confidence

Statement is unsafe for replication with full-text parser plugin

Production Risk

Medium — replica data may diverge from source.

What this means

A DML statement that uses a full-text parser plugin is flagged as unsafe for statement-based replication because the plugin may produce non-deterministic results across different servers.

Why it happens
  1. 1Using MATCH() AGAINST() with a user-defined full-text parser plugin in statement-based replication mode.
How to reproduce
trigger — this will error
trigger — this will error
-- With binlog_format=STATEMENT:
DELETE FROM articles WHERE MATCH(body) AGAINST('keyword');

expected output

Warning (Code 1703): Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement uses a fulltext parser plugin.

Fix

Switch to row-based or mixed replication

Switch to row-based or mixed replication
SET GLOBAL binlog_format = 'ROW';

Why this works

ROW format replicates actual row changes rather than statements, avoiding plugin non-determinism.

What not to do

✕

Sources
Official documentation ↗

MySQL 8.0 — 1703 ER_BINLOG_UNSAFE_FULLTEXT_PLUGIN

Content generated with AI assistance and reviewed for accuracy. Found an error? hello@errcodes.dev

← All MySQL errors