3130
MariaDBERRORNotableDDLHIGH confidence

ALTER TABLE not supported: changing FULLTEXT index requires table copy

Production Risk

Medium — FULLTEXT rebuilds are expensive on large text datasets.

What this means

Adding, dropping, or modifying a FULLTEXT index on a table requires a full table rebuild and cannot be done with ALGORITHM=INPLACE.

Why it happens
  1. 1DROP or ADD FULLTEXT INDEX with ALGORITHM=INPLACE specified.
How to reproduce
trigger — this will error
trigger — this will error
ALTER TABLE articles DROP INDEX ft_idx, ALGORITHM=INPLACE;

expected output

ERROR 3130 (HY000): ALGORITHM=INPLACE is not supported. Reason: Changing a FULLTEXT index requires table copy.

Fix

Use ALGORITHM=COPY

Use ALGORITHM=COPY
ALTER TABLE articles DROP INDEX ft_idx, ALGORITHM=COPY;

Why this works

Full rebuild correctly removes and re-creates FULLTEXT metadata.

What not to do

Sources
Official documentation ↗

MySQL 8.0 — 3130 ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_CHANGE_FTS2

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

← All MariaDB errors