Relationships
#2035 data query omits report artifacts returned by data list and versions
Opened by dieter · 9/5/2026· Shipped 9/7/2026
Summary
Swamp data query does not return report artifacts that are returned by swamp data list, swamp data get, and swamp data versions.
Reproduction
Repository: /home/[REDACTED]/code/dieter-location-tracker Swamp version: 20260904.230512.0-sha.7b111963
swamp data list annotations --json
swamp data versions annotations report-swamp-method-summary --jsonThe list command includes report-swamp-method-summary at version 21. The versions command returns 21 versions.
The equivalent query is:
swamp data query "modelName == \"annotations\" && name == \"report-swamp-method-summary\" && version >= 0" --select "{\"version\": version, \"createdAt\": createdAt, \"size\": size, \"isLatest\": isLatest, \"ownerType\": ownerType, \"workflowName\": workflowName, \"workflowRunId\": workflowRunId, \"jobName\": jobName, \"stepName\": stepName, \"source\": source}" --jsonActual result:
{"results": [], "total": 0, "limited": false}Expected
The query should return the same versions as swamp data versions, including any available provenance fields. The data documentation describes query as the general primitive and documents data versions as the equivalent of a model/name/version query.
Impact
Clients cannot inspect or filter per-version provenance for report artifacts through the data query catalog. Lazyswamp must fall back to swamp data versions, which supplies version numbers but no per-version provenance.
Shipped
Click a lifecycle step above to view its details.