Page MenuHomePhabricator

Isolate and decouple AW Fragment storage to better interact with AW Article Section storage
Closed, ResolvedPublic

Description

Description

Currently, AW Fragments are rendered and stored in the Memcached object cache with the WikilambdaAbstractFragment:... keys (both with and without date).

Fragment getters and setters are spread around different parts of the stack, which complicates any evolution of our Fragment storage layer.

Let's put a bit of work on isolating AWFragment storage now that we are building AWArticle Storage.

AWFragmentStore will surface two methods: a setter and a getter, which internally will do the same as we do now (calling MemcachedWrapper getters and setters)

Details

Event Timeline

gengh claimed this task.

Change #1286283 had a related patch set uploaded (by Genoveva Galarza; author: Genoveva Galarza):

[mediawiki/extensions/WikiLambda@master] [WIP] Isolate and decouple AWFragment Storage

https://gerrit.wikimedia.org/r/1286283

Jdforrester-WMF changed the task status from Open to In Progress.Fri, May 15, 1:41 PM
Jdforrester-WMF triaged this task as Medium priority.

Change #1286283 merged by jenkins-bot:

[mediawiki/extensions/WikiLambda@master] Isolate and decouple AWFragment Storage

https://gerrit.wikimedia.org/r/1286283