hoo created this task. hoo added subscribers: hoo, daniel, aude, JanZerebecki. hoo added a project: Wikidata. Herald added subscribers: StudiesWorld, Steinsplitter, Aklapper.
TASK DESCRIPTION As we will start displaying the commons category in the other projects sidebar soon, we need to discuss finding a way to invalidate the caching for that in case of changes to the Statements in question on Wikidata. The initial implementation wont have any form of cache invalidation, but we certainly need to add that. I can think of a few ways to accomplish that: * Invent "implicit usages" for the Statements (or even Statements in question) that are relevant here. That could even be extended to Sitelinks in order to save EntityUsage entries at some point. This would require some extra logic, but probably not to much. * We could also just have a job or some other nasty thing that totally works around all existing invalidation/ usage/ subscription logic. That would mean we wont suffer any of theses problems, but also a lot of duplicated effort. * Just registering an other usage for all pages on wikis that have the sidebar enabled. That would obviously bloat the EntityUsage significantly (and we already have troubles there) and it would mean by far more cache invalidations. ** It could also be considered splitting up the usages of Statements by property id. That would solve the "number of cache invalidations" problem, but it would totally blow the EntityUsage table. TASK DETAIL https://phabricator.wikimedia.org/T123568 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: hoo Cc: Aklapper, Steinsplitter, StudiesWorld, JanZerebecki, aude, daniel, hoo, Wikidata-bugs, Mbch331 _______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
