EC
3139
MySQLWARNINGCriticalInnoDBMEDIUM confidence

InnoDB: FULLTEXT index does not use a parser plugin

Production Risk

Low — warning only; FULLTEXT index is created without the parser plugin.

What this means

A FULLTEXT index creation was attempted with a WITH PARSER clause, but InnoDB does not support external parser plugins for FULLTEXT indexes. The parser specification is ignored.

Why it happens
  1. 1CREATE FULLTEXT INDEX ... WITH PARSER on an InnoDB table.
How to reproduce
trigger — this will error
trigger — this will error
ALTER TABLE docs ADD FULLTEXT INDEX ft (body) WITH PARSER ngram;

expected output

Warning (Code 3139): InnoDB: FULLTEXT index does not support parser plugin.

Fix

Remove WITH PARSER or use MyISAM

Remove WITH PARSER or use MyISAM
ALTER TABLE docs ADD FULLTEXT INDEX ft (body);

Why this works

InnoDB built-in FULLTEXT parser is used by default.

What not to do

✕

Sources
Official documentation ↗

MySQL 8.0 — 3139 ER_INNODB_NO_FT_USES_PARSER2

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

← All MySQL errors