Change Details

See T261407 for details. The event should contain the page id and page namespace so that it is easy to map to its target elastic index. The data will be stored in elastic within the `predicted_classes` field (currently named `ores_articletopic`, but renaming will happen at some point) along with the the ores predictions already stored there. The frequency of the job is yet to be defined but could be hourly. Once the new event is published, we need to consume it as part of the Elasticsearch update pipeline. The update pipeline itself will need to be modified to support an update frequency other than the current weekly.

See T261407 for details. The event should contain the page id and page namespace so that it is easy to map to its target elastic index. The frequency of the job is yet to be defined but could be hourly. Once the new event is published, we need to consume it as part of the Elasticsearch update pipeline. The update pipeline itself will need to be modified to support an update frequency other than the current weekly.

See T261407 for details. The event should contain the page id and page namespace so that it is easy to map to its target elastic index. The data will be stored in elastic within the `predicted_classes` field (currently named `ores_articletopic`, but renaming will happen at some point) along with the the ores predictions already stored there. The frequency of the job is yet to be defined but could be hourly. Once the new event is published, we need to consume it as part of the Elasticsearch update pipeline. The update pipeline itself will need to be modified to support an update frequency other than the current weekly.