Page MenuHomePhabricator

[Task] Use JOIN to find changes relevant for a given wiki
Open, HighPublic

Description

To find changes relevant to wiki x, we should be able to join wb_changes against wb_changes_subscriptions. This would remove the need for programmatic filtering.

Related Objects

StatusAssignedTask
OpenNone
OpenNone
Resolvedhoo
OpenNone
Resolvedaude
ResolvedNone
Resolvedaude
ResolvedNone
ResolvedLydia_Pintscher
Resolveddaniel
Resolveddaniel
Resolveddaniel
Resolveddaniel
Resolveddaniel
Resolveddaniel
Resolveddaniel
ResolvedNone
Invaliddaniel
Resolveddaniel
Resolveddaniel
Resolveddaniel
Resolveddaniel
Resolveddaniel
Resolveddaniel
Resolvedhoo
DuplicateNone
Resolvedhoo
Resolvedaude

Event Timeline

daniel created this task.Aug 27 2015, 1:52 PM
daniel raised the priority of this task from to Needs Triage.
daniel updated the task description. (Show Details)
daniel added a subscriber: daniel.
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptAug 27 2015, 1:52 PM
Lydia_Pintscher renamed this task from Use JOIN to find changes relevant for a given wiki to [Task] Use JOIN to find changes relevant for a given wiki.Sep 1 2015, 11:39 AM
Lydia_Pintscher triaged this task as Normal priority.
Lydia_Pintscher moved this task from incoming to ready to go on the Wikidata board.
hoo added a subscriber: hoo.Oct 8 2015, 10:18 AM

Is this still relevant?

hoo added a comment.Apr 23 2017, 8:16 PM

Is this still relevant?

Yes, we are actually working on this right now (see the dependency T109825: [Task] Use uppercase entity ID in wb_changes table.).

Restricted Application added a subscriber: PokestarFan. · View Herald TranscriptJul 25 2017, 8:15 AM
hoo added a subscriber: Ladsgroup.Jul 26 2017, 10:55 AM

As far as I can see T111161: Subscribe client wikis immediately after adding sitelinks is the only blocker left for this.

hoo raised the priority of this task from Normal to High.Jul 26 2017, 10:59 AM

Rising priority: Dispatching is an ongoing problem and this will fix (most of?) this.

Also I guess the number of changes that actually need dispatching has decreased (as we have a lot of entities not used on any sister project) these days. Thus fixing this and increasing the job batch size (or completely changing how that works) would fix the dispatching bottleneck for now.