Add the publicly available visitingwatchers/active watchers to labs watchlist_count (Created by T59617).
Description
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Open | Jdrewniak | T128546 [Recurring Task] Update Wikipedia and sister projects portals statistics | |||
Resolved | Krenair | T134017 Create Wikipedia Jamaican | |||
Open | None | T150547 Add visitingwatchers to watchlist_count | |||
Stalled | None | T59617 Make watchlist table available as curated foo_p.watchlist_count on labsdb | |||
Duplicate | None | T93887 Replicate watchlist to labs | |||
Duplicate | None | T106089 Replicate sanitized watchlist table | |||
Resolved | ori | T135029 adywiki and jamwiki are missing the associated *_p databases with appropriate views | |||
Restricted Task | |||||
Resolved | • chasemp | T138450 maintain-replicas.pl unmaintained, unmaintainable |
Event Timeline
Dispenser, thanks for the separate task. If you are ok with that, I will put T59617 as a blocker of this, not a subtask.
The request is reasonable, but this being a very dynamic field it won't be easy. We can expose an approximation, regularly updated, but it will not be perfect. I would strongly suggest using the API if exact results are expected.
If an approximation is ok, but batch access is preferred, this is something that is totally doable and probably we will not get any objection.
I'm fine with stale data. With the API, visitingwatchers represents 0.005 per watcher checked, in total ~3 - 30 second. Is there a way to get a last modified time like with information_schema?
Is there a way to get a last modified time like with information_schema?
Not now, but we could add such information somewhere.