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
F19937109: D18550.id44557.diff
Sun, Apr 12, 6:55 PM
F19918324: D18550.diff
Sat, Apr 4, 3:33 PM
F19918323: D18550.diff
Sat, Apr 4, 3:33 PM
F19914511: D18550.id44557.diff
Fri, Apr 3, 12:04 PM
F19896986: D18550.id.diff
Sun, Mar 29, 6:00 AM
F19827892: D18550.id44586.diff
Mar 9 2026, 1:55 PM
F19826118: D18550.id44586.diff
Mar 8 2026, 5:27 PM
F19820410: D18550.diff
Mar 6 2026, 1:36 PM
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