Page MenuHomePhabricator

Decide to what extent should non-AQS data lookups be allowed in ImpactModule
Open, HighPublic1 Estimated Story Points

Description

Recording an open question from T433352: Review metrics provided by the Impact module and available APIs.

Growth-Team engineers should agree on: In the new Impact module, should non-AQS data lookups be allowed? If so, to what extent?

One of the benefits is to remove the internal DB caching layer, which is unnecessarily complicated. "Challenging" lookups should definitely be in AQS. But what puts us to the level of "challenging"?

Would it be reasonable to read user_editcount from DB? CentralAuth's "global user editcount"? Number of Thanks received?

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript
DMburugu renamed this task from Decide to what extend should non-AQS data lookups be allowed in ImpactModule to Decide to what extent should non-AQS data lookups be allowed in ImpactModule.Aug 10 2026, 10:59 AM
Michael set the point value for this task to 1.Aug 11 2026, 3:26 PM