Get Report Run Partition Metrics

GET 
/reports/:run_id/partitions/metrics

Metrics actually scored on each partition of this run — every partition in one read.

{partition_id: [metric, ...]}, via get_run_partition_metrics (AIP-5429): the same per-measurement identity derivation report generation already uses, not a parallel join. Bulk rather than one-partition-at-a-time on purpose — AIP-5389 puts a metric picker on every partition, and a per-partition GET would open a fresh DuckDB connection and re-read the run's Parquet from object storage once per partition selected. This reads it once. Answers "was this scored here" — whether a metric can ever run on a partition's target kind is a separate, pre-run question (partition_available_metrics).

Lives under /reports/{run_id}/... rather than /runs/{run_id}/... even though it touches no Report row, to sit beside AIP-5385's partition listing (above): the report wizard is this endpoint's only caller, and grouping by caller beats strict resource modelling here.

Empty, never an error, for a wide run or a run with no output yet.

Not gated by ensure_report_source_run: this reads the run's own analytics output, which exists independently of whether the run's pipeline is (yet) an eligible report source.

Note: the explicit run-existence check below is load-bearing for platform admins — see get_report_questions.

Request

Responses

200

Successful Response

422

Validation Error