ASAPQuery's SQL parser currently requires the SELECT clause to contain exactly one projection item i.e. the aggregate function. Any query that names group-by columns alongside the aggregate is rejected.
Currently Supported -
SELECT quantile(0.99)(pkt_len) AS p99_pkt_len FROM netflow_table GROUP BY proto, srcip, dstip
Needed Support -
Standard SQL grouped aggregate queries should also be supported.
SELECT proto, srcip, dstip, quantile(0.99)(pkt_len) AS p99_pkt_len FROM netflow_table GROUP BY proto, srcip, dstip
Scope
This change is limited to the sql_utilities parser. No execution or aggregation logic needs to change. Once parsed, a query with multiple projection columns should behave exactly the same as the current single-aggregate form, using the existing group-by labels and precomputed aggregation lookup path.
ASAPQuery's SQL parser currently requires the SELECT clause to contain exactly one projection item i.e. the aggregate function. Any query that names group-by columns alongside the aggregate is rejected.
Currently Supported -
SELECT quantile(0.99)(pkt_len) AS p99_pkt_len FROM netflow_table GROUP BY proto, srcip, dstipNeeded Support -
Standard SQL grouped aggregate queries should also be supported.
SELECT proto, srcip, dstip, quantile(0.99)(pkt_len) AS p99_pkt_len FROM netflow_table GROUP BY proto, srcip, dstipScope
This change is limited to the
sql_utilitiesparser. No execution or aggregation logic needs to change. Once parsed, a query with multiple projection columns should behave exactly the same as the current single-aggregate form, using the existing group-by labels and precomputed aggregation lookup path.