After https://gerrit.wikimedia.org/r/#/c/334194/ is deployed, we want to reindex Wikidata so that new labels indexes are created.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Wikidata-bugs | T77898 query taking 10s: TermSqlIndex::getMatchingIDs | |||
| Open | None | T46529 Wikidata search problems (tracking) | |||
| Resolved | Smalyshev | T78157 [Story] Use ElasticSearch for entity search on wikidata.org | |||
| Declined | None | T170392 Create gadget that enables the use of the elastic search backend for the entity selector | |||
| Open | None | T170547 Metrics to evaluate new search for item suggestor | |||
| Declined | None | T170549 Provide A/B test for item suggestor | |||
| Resolved | Smalyshev | T162292 Reindex wikidata to pick up labels/descriptions mappings | |||
| Resolved | dcausse | T160926 Make noop script be able replace whole fields with nested subfields | |||
| Resolved | dcausse | T166589 Update wikidata code to take advantage of nested fields noop script |
Event Timeline
Comment Actions
@Smalyshev It seems it would be useful if we could test the cirrus backend for wbsearchentities on the live site, by setting the useCirrus parameter via a Gadget. For that, we'll need the new data in the Elastic index. Are there any remaining blockers for rebuilding the index? Can you give us some idea of when this could happen? Before Wikimania would be nice...
Comment Actions
I understand the code hasn't been deployed yet (wikidata deployment schedule is still a mystery to me, I don't think there's a calendar anywhere?). So we're waiting for the code being deployed. As soon as everything is there, I'll do the reindexing.
Comment Actions
Turns out this reindex needs full (not in-place) reindex, because we need to load descriptions into the index. So it will probably take more time. Reopening for now.