Pin reporting datasets to published Dataflow runs

This commit is contained in:
2026-08-04 12:48:37 +02:00
parent aebe94ecc2
commit 4e0238f701
6 changed files with 84 additions and 1 deletions
+4
View File
@@ -27,6 +27,10 @@ published by a source-owning module. Do not expose another module's ORM or an
unbounded SQL connection as a report source. Configure an explicit schema,
freshness policy, source fingerprint expectations, purpose, privacy,
retention, and a row-policy provider where source access alone is not enough.
For a Dataflow source, `source_run_ref` optionally pins one successful run that
published an immutable Datasource materialization. Reporting passes this pin
through rather than re-executing the pipeline. The current principal must still
be authorized for the Dataflow definition and the exact Datasource output.
On PostgreSQL installations, Reporting compiles bounded semantic filters,
grouping, measures, calculated measures, ordering, offsets, and limits into a