mirror of
https://github.com/GreptimeTeam/greptimedb.git
synced 2026-11-18 00:34:11 +00:00
* test(query): pin the aggregate plan shapes the uniform topology builds Four native-aggregate integration tests have failed on `narthex` since the uniform native PromQL topology landed (#10418): their plan-shape helpers demanded the pre-topology chains, panicked before the native-vs-legacy comparison ran, and nextest's fail-fast then left most of the suite unexecuted. Both shapes the helpers now see are the topology's own: - a Partial producer the analyzer keeps above the regions reads the `MergeScanExec` through one `SeriesRepartitionExec` that widens the region stream to `target_partitions` with `RawPrimaryKey`, so each stored key still reaches exactly one owner; - a single-owner Final reads the Partial producer itself through its state router, instead of a region merge scan, because both halves are planned in the frontend tree now. Pin each chain exactly rather than accepting any exchange, and run the legacy comparison before the shape assertions so a shape regression can no longer hide the result check. Verified: native_aggregate 6/6, native_promql 90/94 (the four `integration_http_s3*` cases abort for environment reasons), clippy and fmt clean. Signed-off-by: discord9 <discord9@163.com> * test(query): read one raw source per selector occurrence in the CTE case `cte_native_statement_runs_the_fused_plan` asserted that one logical table keeps both occurrences of a repeated selector region-local, so no raw source appears in the plan. The uniform topology reads every selector through its own raw source, so the statement now names two. Pin that instead: both occurrences still read their own region scan, and each does it through a raw source of its own. Signed-off-by: discord9 <discord9@163.com> --------- Signed-off-by: discord9 <discord9@163.com>