Page MenuHomePhabricator

Build a prototype fulltext engine ("Ferret") using only basic MySQL primitives
ClosedPublic

Authored by epriestley on Aug 28 2017, 9:35 PM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Mar 28, 4:03 AM
Unknown Object (File)
Tue, Mar 12, 10:43 PM
Unknown Object (File)
Sun, Mar 10, 1:44 AM
Unknown Object (File)
Feb 3 2024, 4:33 PM
Unknown Object (File)
Dec 27 2023, 11:58 AM
Unknown Object (File)
Dec 27 2023, 11:58 AM
Unknown Object (File)
Dec 27 2023, 11:58 AM
Unknown Object (File)
Dec 21 2023, 8:50 PM
Subscribers
None

Details

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".

Screen Shot 2017-08-28 at 2.26.28 PM.png (740×434 px, 54 KB)

Diff Detail

Repository
rP Phabricator
Branch
ferret1
Lint
Lint Passed
Unit
Tests Passed
Build Status
Buildable 18190
Build 24458: Run Core Tests
Build 24457: arc lint + arc unit