Page MenuHomePhabricator

Document how to write a search extension
Open, LowPublic

Description

Category:Search extensions says

The Search extensions category contains articles on extensions that extend or modify the search behavior of MediaWiki. For guidance in writing and selecting search extensions, please see Manual:Search.

but then the page doesn't actually exist. It would be nice to have high-level documentation on this. Looking at CirrusSearch it seems like such extensions are supposed to a mix of hooks and subclassing, neither of which is easy to find or documented much even inline. Just having a list of the right hooks and classes with one-liner explanations of what they do would be a great improvement; having some examples would be even better.

It would be extra nice if the page also explained all the ways other extensions can interact with search (metadata in media handlers, content handlers etc).

Event Timeline

Search should be doable only by implementing the SearchEngine class in core, the addition of hooks for various additional features are not critical to implementing a search engine, they just gives us extra features or flexibility. I don't know if anyone on the search team will have time to write this documentation, it would take us similar amounts of time as external users as from the Cirrus side it's not clear where the deliniation is between required and necessary features.

MPhamWMF subscribed.

Closing out low/est priority tasks over 6 months old with no activity within last 6 months in order to clean out the backlog of tickets we will not be addressing in the near term. Please feel free to reopen if you think a ticket is important, but bare in mind that given current priorities and resourcing, it is unlikely for the Search team to pick up these tasks for the indefinite future. We hope that the requested changes have either been addressed by or made irrelevant by work the team has done or is doing -- e.g. upgrading Elasticsearch to a newer version will solve various ES-related problems -- or will be subsumed by future work in a more generalized way.

Dzahn subscribed.

Having documentation is literally bug 1(!) in Bugzilla.