Page MenuHomePhabricator

Consider using CombinedEntitySearchHelper with EntitySearchElastic and EntityIdSearchHelper for
Closed, ResolvedPublic


During T219364 users were not able to use entities that they created for a rough 24 hour period.

11:03 AM <+gehel> lag of multiple hours is unexpected and **should** not happen (or if it does, it should be treated as a bug)
11:04 AM <+gehel> but lag of < 1h is perfectly normal

We should consider using a combined search again allowing users to use entities that they create moments after creating them rather than needing to worry about cirrus search lag.
We could also consider some clever JS that when just and entity id is entered, detect this somehow and allow the user to try sending the edit request which would then be validated on the server side?
We could also have some sort of fallback if we detect that the cirrus search returned no results and is lagged?

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptMar 27 2019, 11:15 AM
Addshore added a subscriber: Smalyshev.

We used to have this but @Smalyshev removed it I think? So adding him back here so we can discuss options / thoughts.

I think this is what 2385879c4d64e027a4122aee20655e365628f6ef in WikibaseCirrusSearch did?

Addshore closed this task as Resolved.Jun 22 2019, 2:42 PM
Addshore claimed this task.

I believe so!

Restricted Application added a project: User-Addshore. · View Herald TranscriptJun 22 2019, 2:42 PM