ProofreadPage Index: pages have all a specific kind of Wikitext content (a template call with parameters) and a customised editing interface. It would make sense to implement the ContentHandler abstraction to them. The current pages should be moved from the Wikitext content model to the new one.
Description
Description
Details
Details
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Use ContentHandler for index pages | mediawiki/extensions/ProofreadPage | master | +937 -2 |
Event Timeline
Comment Actions
Change 328543 had a related patch set uploaded (by Tpt):
[mediawiki/extensions/ProofreadPage@master] Use ContentHandler for index pages
Comment Actions
@DBA Change https://gerrit.wikimedia.org/r/#/c/328543/ contains a maintenance script to migrate old Index: pages to the new content model. Is it possible to get a code review for it? It will affect all wikis where ProofreadPage is deployed (i.e. all Wikisources).
A such script have been used for migrating the Page: pages: https://phabricator.wikimedia.org/diffusion/EPRP/browse/master/maintenance/fixProofreadPagePagesContentModel.php
Comment Actions
How much activity do you predict to have (I do not need an accurate count, just if it is thousands or millions or revisions).
Comment Actions
The biggest Wikisources have less than 20,000 Index: pages each. So on all wikis combined it is something around ~100,000 rows.
Comment Actions
A first look from the database point of view looks fine -activity is batched, and wait for slaves is run after every batch. Please allow me a few extra days to give a closer look at the query run to see if there could be an optimization problem (that only tends to arise when tested with lots of production data).
I do not know much about the mediawiki high level model (ContentHandler), so I hope someone other than me is on top of that.
Comment Actions
Change 328543 merged by jenkins-bot:
[mediawiki/extensions/ProofreadPage@master] Use ContentHandler for index pages