Page MenuHomePhabricator

Create and populate a stopwords table for InnoDB fulltext indexes to use in the future
ClosedPublic

Authored by epriestley on Nov 24 2016, 4:43 PM.
Tags
None
Referenced Files
F19612771: D16940.diff
Tue, Feb 3, 7:42 PM
F19467970: D16940.diff
Jan 3 2026, 8:49 PM
F19244373: D16940.id40773.diff
Dec 22 2025, 12:58 AM
F19128371: D16940.id40773.diff
Dec 10 2025, 3:42 AM
F19064222: D16940.diff
Nov 29 2025, 8:23 PM
F18840840: D16940.id.diff
Oct 28 2025, 4:14 AM
F18839979: D16940.diff
Oct 27 2025, 8:22 PM
F18817695: D16940.id40773.diff
Oct 21 2025, 5:38 PM
Subscribers
None

Details

Summary

Ref T11741. InnoDB uses a stopwords table instead of a stopwords file.

During storage upgrade, synchronize the table from the stopwords file on disk.

Test Plan
  • Ran storage upgrade.
  • Ran select * from stopwords, saw stopwords.
  • Added some garbage to the table.
  • Ran storage upgrade, saw it remove it.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Create and populate a stopwords table for InnoDB fulltext indexes to use in the future.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)

We don't actually end up really needing this since the InnoDB stopwords are pretty reasonable, but I wrote it and it could make things easier in the future (e.g., it lets us tell users to change one setting to enable it). If it creates any maintenance headaches I'll just throw it out.

chad edited edge metadata.
This revision is now accepted and ready to land.Nov 24 2016, 6:53 PM
This revision was automatically updated to reflect the committed changes.