Page MenuHomePhabricator

Prepare for InnoDB FULLTEXT support
ClosedPublic

Authored by epriestley on Nov 24 2016, 6:03 PM.
Tags
None
Referenced Files
F14030391: D16942.id40786.diff
Sat, Nov 9, 3:10 AM
F14014624: D16942.id40786.diff
Sun, Nov 3, 6:25 AM
F14005649: D16942.id40786.diff
Sun, Oct 27, 5:24 PM
F13998400: D16942.diff
Thu, Oct 24, 9:20 AM
F13995847: D16942.id40775.diff
Wed, Oct 23, 4:02 PM
F13968279: D16942.diff
Oct 16 2024, 7:50 PM
F13955369: D16942.id40786.diff
Oct 14 2024, 1:04 AM
Unknown Object (File)
Oct 9 2024, 6:23 AM
Subscribers
None

Details

Summary

Ref T11741. This makes everything work if we switch to InnoDB, but never actually switches yet.

Since the default minimum word length (3) and stopword list (36 common English words) in InnoDB are generally pretty reasonable, I just didn't add any setup advice for them. I figure we're better off with simpler setup until we identify some real problem that the builtin stopwords create.

Test Plan

Swapped the false to true, ran storage adjust, got InnoDB fulltext indexes, searched for stuff, got default "AND" behavior.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Prepare for InnoDB FULLTEXT support.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: chad.
chad edited edge metadata.
This revision is now accepted and ready to land.Nov 24 2016, 6:16 PM
This revision was automatically updated to reflect the committed changes.