Skip to main content
← Back to list
01Issue
FeatureShippedSwamp CLI
Assigneesstack72

Relationships

#919 catalog backfill should support scoped population for targeted lookups

Opened by stack72 · 7/2/2026· Shipped 7/3/2026

When data.latest() falls back to the catalog path (orphan data without a matching definition), the catalog triggers a full findAllGlobal() backfill that walks every metadata.yaml in the datastore. This is the same O(N) cost that swamp-club#918 eliminated from the common path.

The catalog's populate-everything-before-answering-anything model means any first catalog query pays the full datastore scan cost, even when the query only needs one specific (modelName, dataName) pair.

A scoped backfill — or an indexed lookup that works without prior population — would let data.latest() stay O(1) even in the orphan/no-definition edge case.

02Bog Flow
OPENTRIAGEDIN PROGRESSSHIPPED+ 1 MOREASSIGNED+ 5 MOREREVIEW+ 4 MOREPR_MERGED+ 1 MORENOTIFICATION_SKIPPED

Shipped

7/3/2026, 9:27:09 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
stack72 assigned stack727/3/2026, 6:03:09 PM

Sign in to post a ripple.