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.
- Mentioned In
- T63111: Convert primary key integers and references thereto from int to bigint (unsigned)
T301039: Provide a dump of PDF/DjVU metadata
T297633: <Tech Initiative> Improving Databases in MediaWiki
T261889: Use a BlobStore for storing var dumps
T241312: Remove support for wgLegacySchemaConversion and HistoryBlobCurStub
T106363: Migrate Flow content to new separate logical External Store in production
T220493: Xml stubs dumps are running 5 to 15x slower than previously
T183487: MCR schema migration stage 3: stop using legacy fields
T199121: RFC: Spec for representing multiple content objects per revision (MCR) in XML dumps
- Mentioned Here
- T106363: Migrate Flow content to new separate logical External Store in production
Change 538599 restored by Daimona Eaytoy:
Use a BlobStore for storing var dumps.
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?