EC
1655
MariaDBERRORCommonReplicationHIGH confidence

Error parsing conflict function specification in ndb_replication table

Production Risk

High — NDB conflict detection will not work until the function is corrected.

What this means

The conflict_fn column in the ndb_replication table contains a value that cannot be parsed as a valid NDB conflict function specification.

Why it happens
  1. 1Syntax error in the conflict_fn value in the ndb_replication table.
  2. 2Unknown or unsupported conflict function name.
How to reproduce
trigger — this will error
trigger — this will error
UPDATE mysql.ndb_replication SET conflict_fn = 'NDB$INVALID()' WHERE db = 'mydb';

expected output

ERROR 1655 (HY000): Error parsing conflict function specification.

Fix

Correct the conflict function specification

Correct the conflict function specification
UPDATE mysql.ndb_replication
  SET conflict_fn = 'NDB$MAX(timestamp_col)'
  WHERE db = 'mydb' AND table_name = 'mytable';

Why this works

Using a valid built-in NDB conflict function name and syntax resolves the parse error.

Version notes

Sources
Official documentation ↗

MySQL 8.0 — 1655 ER_CONFLICT_FN_PARSE_ERROR

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

← All MariaDB errors