Page MenuHomePhabricator

Coalesce change events before injecting them into the recentchanges table
Closed, ResolvedPublic


The pollForChanges should coalesc (combine/collapse) successive changes done by the same user to the same item. This avoids clutter in the recentchanges table (and thus in the watchlist), and also reduces overhead for notifying client wikis about changes.

Note that some information from the edit comment may be lost; or perhaps the summaries for each edit can be stored in the rc_params field of the recentchanges table and later be used for rendering the RC item be type appropriate hook.

See also

Version: unspecified
Severity: normal
See Also:



Event Timeline

bzimport raised the priority of this task from to Medium.Nov 22 2014, 1:11 AM
bzimport set Reference to bz42189.
bzimport added a subscriber: Unknown Object (MLST).

Note: This is related to but not at all the same as bug 42065. In fact, to improve performance, both should be done: coalescing change events and skipping redundant update jobs.

If coalescing makes it difficult to keep the comments somehow then a link could be added to include the comments through ajax calls. To make that work it would be necessary to add from-to/start-end times or revisions.

Verified in Wikidata demo sprint 31