Page MenuHomePhabricator

Use the Ferret engine fulltext document table to drive auxiliary fulltext constraints
ClosedPublic

Authored by epriestley on Sep 7 2017, 3:49 PM.
Tags
None
Referenced Files
F13050137: D18550.id44586.diff
Fri, Apr 19, 2:38 AM
F13050136: D18550.id44557.diff
Fri, Apr 19, 2:38 AM
F13050135: D18550.id.diff
Fri, Apr 19, 2:38 AM
Unknown Object (File)
Thu, Apr 11, 10:53 AM
Unknown Object (File)
Thu, Apr 11, 3:59 AM
Unknown Object (File)
Mar 16 2024, 9:52 AM
Unknown Object (File)
Mar 15 2024, 1:51 PM
Unknown Object (File)
Mar 1 2024, 3:05 AM
Subscribers
None

Details

Summary

Ref T12819. I started trying to get individual engines to drive these constraints (e.g., ManiphestTaskQuery can do most of the work) but this is a big pain, especially since most engines don't support "any owner" or "no owner", and not everything has an owner, and so on and so on. Going down this path would have meant a huge pile of stub functions everywhere, I think.

Instead, drive these through the main engine using the fulltext document table, which already has everything we need to apply these constraints in a uniform way.

Also tweak some parts of query construction and result ordering.

Test Plan

Searched for documents by author, owner, unowned, any owner, tags, subscribers, fulltext in global search. Got sensible results without any application-specific code.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable