Page MenuHomePhabricator

Implement buffering in DispatchingTermLookup
Closed, ResolvedPublic

Description

Following up T149583 BufferingTermLookup(s) used in client should work with foreign entity ids.
We need to figure out how to handle buffering with multiple repositories.

Related Objects

StatusSubtypeAssignedTask
Declineddchen
OpenNone
OpenNone
DuplicateNone
OpenFeatureNone
OpenFeatureNone
DuplicateNone
ResolvedNone
ResolvedNone
ResolvedNone
OpenNone
OpenNone
StalledNone
ResolvedLydia_Pintscher
ResolvedLydia_Pintscher
ResolvedLydia_Pintscher
ResolvedLydia_Pintscher
ResolvedWMDE-leszek
ResolvedWMDE-leszek
ResolvedJakob_WMDE
ResolvedWMDE-leszek

Event Timeline

We should probably use this opportunity to unwind how caching works inside of the various term related services.

You might want to make BufferingTermLookup a general wrapper around another EntityTermLookupBase (instead of it using a TermIndex directly).

Please keep in mind that the defining feature of BufferingTermIndex is prefetching, not caching. It's related, but different, concern.

Please keep in mind that the defining feature of BufferingTermIndex is prefetching, not caching. It's related, but different, concern.

True… the name doesn't really reflect that, though. Often it's enough to have a caching service that allows batch lookups to implement pre-fetching, I guess that is also true here.

Please see me implementation notes in T148141#2760606

Change 320225 had a related patch set uploaded (by Jakob):
WIP: Add DispatchingTermBuffer.

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

Change 320225 merged by jenkins-bot:
Add DispatchingTermBuffer.

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