fix(asap-planner): use MinMax with grouping for 1s spatial SQL MIN/MAX instead of MultipleMinMax

[akanksha-akkihal]

Code Changes Summary

asap-planner-rs/src/planner/sql.rs

Before (default behavior)

Spatial MIN / MAX queries used:

• Aggregation: MultipleMinMax
• grouping: []
• aggregated: [GROUP BY columns]
• rollup: [other metadata columns]

---

After

• Introduced let mut configs to allow post-processing updates

• Spatial MIN / MAX fix
  (applies only to QueryType::Spatial + "MIN" / "MAX"):

  • aggregation_type → MinMax
  • aggregation_sub_type → "min" or "max"
  • grouping_labels → SQL GROUP BY columns (spatial_output)
  • aggregated_labels → []
  • rollup_labels → []

---

Unchanged

• Temporal / spatiotemporal MIN / MAX still use MultipleMinMax

---

asap-planner-rs/tests/sql_integration.rs

New Test: spatial_max_pkt_len

• Query:
  MAX(pkt_len) ... GROUP BY dstip (1-second window, netflow_table)

---

Runtime Impact (Generated Config)

Field	Before	After
Type	MultipleMinMax	MinMax
grouping	[]	[dstip] (GROUP BY cols)
aggregated	[dstip]	[]
rollup	e.g. [srcip, proto]	[]

---

Result

• Aligns planner output with:
  • query engine expectations
  • ingest sharding (group-by as store key)

[akanksha-akkihal]

Not fixing. Requirements changed.