Page MenuHomePhabricator

Ensure Search endpoint results are consistent regardless of database result ordering
Open, Needs TriagePublic

Description

Given the following scenario, the REST API Search endpoint is returning different results depending on result order from the database (as seen when testing with Sqlite and MySQL databases)

  • A Redirect Source and Redirect Target page both contain text that matches the search query (e.g. /search/title?q={the_query})

Current Behavior:

  • Depending on the ordering of the results from the database, the matched_title field may or may not be populated

Expected Behavior:

  • The matched_title field is either consistently null or consistently populated

Details

Event Timeline

Change 866551 had a related patch set uploaded (by Kosta Harlan; author: Kosta Harlan):

[mediawiki/core@master] api-testing: Skip flaky Search.js tests

https://gerrit.wikimedia.org/r/866551

Change 866551 abandoned by Kosta Harlan:

[mediawiki/core@master] api-testing: Skip flaky Search.js tests

Reason:

https://gerrit.wikimedia.org/r/866551

AGhirelli-WMF added a project: CirrusSearch.
AGhirelli-WMF subscribed.

Tagging Search team to look into

Are there some examples API requests we could look at? That would help pin down what exactly the problem is here.