Currently, the change dispatcher uses sitelinks (wb_items_per_site). With arbitrary item access, this is no longer sufficient. The wb_changes_subscription table has the relevant information now.
Version: unspecified
Severity: normal
Whiteboard: u=dev c=backend p=5
| Status | Subtype | Assigned | Task | |
|---|---|---|---|---|
| · · · | ||||
| Resolved | Lydia_Pintscher | T49288 [Epic] Track Wikidata entity usage on client pages | ||
| Resolved | daniel | T73052 Introduce a "entity change subscription" service | ||
| Resolved | daniel | T66590 Usage Tracking: change dispatcher should use the wb_changes_subscription table | ||
| Invalid | None | T88419 Feature switch for using subscription mechanism for change propagation. | ||
| Resolved | daniel | T90755 Implement hybrid mode for change dispatcher, which uses both wb_items_per_site and wb_changes_subscription. | ||
| Resolved | daniel | T70380 Factor dispatch logic out of maintenance script | ||
| · · · |
Change 202386 had a related patch set uploaded (by Daniel Kinzler):
Hook up subscription lookup based on settings.
Change 202372 had a related patch set uploaded (by Daniel Kinzler):
Introduce SqlSubscriptionLookup