This is mostly already possible with the useChangesTable setting, but perhaps the default should be changed.
Other operations around the table should also be checked
acceptance criteria:🏕️🌟
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | karapayneWMDE | T265198 Don’t require extra cronjobs / maintenance scripts for Wikibase | |||
| Declined | None | T272357 [Story] Allow wikibases to not populate the wb_changes table if it is not going to be used |
This was raised with Sam has having a possible negative user impact and Sam thanks us for that.
Part of this ticket should include notes that we would include in the release notes (this default is changing, and this is what it means)
In ticket polishing we also discussed the fact that we could probably add a nice little warning to the 2 maintenance scripts that interact with this table if they get run and this setting is false!
I'm not quite understanding what this is supposed to be fixing. Would changes in Wikibase Items trigger a cache purge of local sitelink'ed pages, without having to set up the whole notification system?
FWIW, I don’t think the default should change at all. Once T272356 is done, the size of the wb_changes table should stay within reasonable limits anyways – it’s nice if site admins can prune it even further by disabling writes to it if they want, but I don’t think change dispatching should be broken by default.