Page MenuHomePhabricator

ParserOutputAccess should use a separate ParserCache instance for Parsoid output
Closed, ResolvedPublic


Since we may not always have enough capcity to store regular parser output and parsoid output on the same ParserCache backend, we need ParserOutputAccess to have the ability to use a different ParserCache instance of parsoid output. Such a different instance already exists, it is currently used by ''Parsoid''OutputAccess.

Implementation draft: instead of injecting a ParserCache instance into ParserOutoutAccess, inject a ParserCacheFactory. ParserOutoutAccess can then detect whether we will be using parsoid (see T300190), and select the appropriate ParserCache instance accordingly.

Related Objects

Event Timeline

Change 883501 had a related patch set uploaded (by D3r1ck01; author: Derick Alangi):

[mediawiki/core@master] ParserOutputAccess: Detect and set appropriate primary cache

DAlangi_WMF moved this task from Unsorted to Parsoid pile on the RESTBase Sunsetting board.

Change 883501 merged by jenkins-bot:

[mediawiki/core@master] ParserOutputAccess: Fork primary and secondary caches for parsoid