epriestley f97157e7ed Build a prototype fulltext engine ("Ferret") using only basic MySQL primitives ... Summary: Ref T12819. I gave this stuff a sweet code name because all the terms related to "fulltext" and "search" already mean 5 different things. It, uh, ferrets out documents for you? I'm building this to work a lot like the existing ngram index, which seems to work pretty well. If this sticks, it will auto-resolve the join issue (in T12443) by letting us do the entire thing locally in a JOIN and thus dodge a lot of mess. This index gets built alongside other indexes, but only shows up in the UI if you have prototypes enabled. If you do, it appears under the existing fulltext field in Maniphest. No existing functionality is affected or disrupted. NOTE: The query engine half of this is still EXTREMELY primitive, and this probably performs worse than the existing field for now. If this doesn't show obvious signs of being awful on `secure` I'll improve that in followup changes. Test Plan: Indexed my tasks, ran some simple queries, got the results I wanted, even for queries "ko", "k", "v0.1". {F5147746} Reviewers: chad Reviewed By: chad Maniphest Tasks: T12819, T12443 Differential Revision: https://secure.phabricator.com/D18484		2017-08-28 14:52:59 -07:00
..
autopatches	Build a prototype fulltext engine ("Ferret") using only basic MySQL primitives	2017-08-28 14:52:59 -07:00
patches	Migrate Project status to modular transactions	2017-05-18 11:36:13 -07:00
quickstart.sql	Regenrate Quickstart SQL	2017-04-23 11:04:02 -07:00
stopwords.txt	Provide a setup warning about using the default MySQL stopword file	2014-08-13 15:34:09 -07:00
stopwords_myisam.txt	Show users how fulltext search queries are parsed and executed; don't query stopwords or short tokens	2017-04-12 19:07:54 -07:00