Pchelolo added a comment.

From the #services side there are 2 things to consider:

  1. Invalidation. Right now we do not have summaries for wikidata, so new rules will need to be added to #changeprop for cache invalidation. In case we include information like number of sitelinks etc, that's not actually changed by editing the item, we would need to thinkhow to track that information and invalidate it. Also, the normal summary endpoint is based on Parsoid HTML while the wikidata endpoint will likely be based on MW API, so it will need special invalidation rules.
  1. Storage. If we want to use the endpoint for Page Previews, we either need to store it in all the languages, or we need to make it fast enough so that the cache miss is acceptably quick to generate on the fly. Let's benchmark it when the endpoint is done, but regardless of the result, most likely we will not be able to store it as Cassandra right away because of capacity issue.

TASK DETAIL
https://phabricator.wikimedia.org/T199096

EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/

To: Pchelolo
Cc: Pchelolo, Liuxinyu970226, Aklapper, ovasileva, bearND, Jdlrobson, Jhernandez, Lydia_Pintscher, Nirzar, Kotchchanipa, Adrian1985, Abo00tamr, Lahi, Gq86, GoranSMilovanovic, Jayprakash12345, QZanden, LawExplorer, Mholloway, Eevans, mobrovac, Hardikj, Wikidata-bugs, aude, Ricordisamoa, Jdforrester-WMF, Mbch331
_______________________________________________
Wikidata-bugs mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs

Reply via email to