Skip to content

fix(service-analytics)!: the cube door asks the aggregate × field-type table for every measure (#21044) #29937

fix(service-analytics)!: the cube door asks the aggregate × field-type table for every measure (#21044)

fix(service-analytics)!: the cube door asks the aggregate × field-type table for every measure (#21044) #29937

Triggered via pull request October 1, 2026 08:20
Status Success
Total duration 1m 4s
Artifacts –

pr-automation.yml

on: pull_request
Check PR Size
20s
Check PR Size
Check Changeset
1m 0s
Check Changeset
Auto Label
17s
Auto Label
Fit to window
Zoom out
Zoom in

Annotations

4 notices
Check PR Size
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"
Auto Label
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"
Check Changeset: .changeset/21044-cube-measure-field-type-table.md#L0
ADR-0087 exemption (already-registered): the pairs this change refuses are exactly the pairs AGGREGATE_FIELD_TYPE_COMPATIBILITY already refuses, and the table is not edited: every refused min / max pair is registered under protocol major 18 by the first id and every refused sum / avg pair by the second, each with its routes (count, a sort for a first or last record, or a numeric / temporal field for a quantity stored as text). This change adds a query-time reader of the same table at the analytics cube door; it refuses a query shape, not a stored one, and no authorable key, export or stored row moves: CubeSchema and the analytics query body keep parsing every member.
Check Changeset
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"