For making articles searchable via topic, ElasticSearch needs to index them via ORES drafttopic scores. ORES predictions come in the form of a topic name -> probability map (example); the best tool to implement them in ElasticSearch seems to be a text field, with topics stored as words and scores as word frequencies (meaning probabilities need to be scaled and rounded to some integer range; 0-1000 should be accurate enough).
|mediawiki/vagrant : master||Enable ORES articletopic handling in cirrussearch role|
|operations/mediawiki-config : master||Enable ores_articletopics field for all wikis|
|mediawiki/extensions/CirrusSearch : master||Add ores_drafttopics field mapping|
|mediawiki/extensions/GrowthExperiments : master||Add ores_drafttopics field mapping|
|operations/mediawiki-config : master||[cirrus] add elastic mapping for ores drafttopics|
|Open||None||T240517 [EPIC] Growth: Newcomer tasks 1.1.1 (ORES topics)|
|Open||None||T240558 Update ORES drafttopic data score in ElasticSearch when an article gets edited|
|Open||dcausse||T240550 Add mapping for ORES topic field in ElasticSearch|
- Mentioned In
- T240556: Load ORES articletopic data into ElasticSearch via the weekly bulk update
T147505: [EPIC][Recurring task] CirrusSearch: what is updated during re-indexing
T240517: [EPIC] Growth: Newcomer tasks 1.1.1 (ORES topics)
- Mentioned Here
- T243357: Once the ORES articletopic - ElasticSearch pipeline is set up, update data about all articles
This is still waiting for an in-place reindex before it is queryable. We were waiting on wmf.19 and an unrelated mapping change before running that. Now that that change is deployed along with this one we should be able to run the re-index this week.
Does that block T243357: Once the ORES articletopic - ElasticSearch pipeline is set up, update data about all articles? I figured we could do it now so we don't have to wait a week for the full dataset.