We should migrate data stored in the External Store away from the text table: The External Store URL that is contained in the text blob can be written to the cont_address field (possibly with a prefix, to be decided, see External Store Integration). Then the corresponding rows can be deleted from the text table.
Description
Details
Subject | Repo | Branch | Lines +/- | |
---|---|---|---|---|
Use a BlobStore for storing var dumps | mediawiki/extensions/AbuseFilter | master | +24 -92 |
Event Timeline
Maybe related or blocker: T106363
I am interested on this happening at some point, I just saw lots of revision data (not metadata) stored on the text table and its impact on a quick database recovery.
Change 538599 had a related patch set uploaded (by Daniel Kinzler; owner: Daniel Kinzler):
[mediawiki/extensions/AbuseFilter@master] Use a BlobStore for stroing var dumps.
Change 538599 abandoned by Daniel Kinzler:
Use a BlobStore for storing var dumps.
Reason:
see I22cf698c5be77506727cbd227c67e037a5d89b5c
Change 538599 restored by Daimona Eaytoy:
Use a BlobStore for storing var dumps.
Reason:
This can be rebased on top of I4444cada720ab62d187f2dd0c4760697e465f2ff to remove any concern about back-compat stuff.
@daniel would you like to do that yourself, or should I revamp this patch and you/CPT will review?
Change 538599 merged by jenkins-bot:
[mediawiki/extensions/AbuseFilter@master] Use a BlobStore for storing var dumps
While doing the migration itself is a lot of work, making new revisions directly link to ES in content table should be rather easy and it would at least stop the table to grow even larger. Does anyone feel like doing that part?