Enable Parallel Aggregation for Non-Overlapping Partitioned Data

[gene-bordegaray]

Will finish later

Which issue does this PR close?

• Closes Enable Parallel Aggregation for Non-Overlapping Partitioned Data #18777.

Rationale for this change

What changes are included in this PR?

Are these changes tested?

Benchmark results:

TPCH remains unchange as expected since the files don't use Hive-Partitioning

I created my own benchmark using partitioned by partitioning spf1 and spf10 benches to use the optimizations. This benchmark ran the query:

Query 'Group By Partition Col': Results MATCH
Query 'Group By Partition+Val': Results MATCH
Query 'Group By Non-Partition Col': Results MATCH
Validation detailed output written to hive_partitioned_benchmark_output.txt
Benchmarking hive_partitioned_agg/preserve_partition_values=true: Collecting 100 samples in
hive_partitioned_agg/preserve_partition_values=true
                        time:   [14.630 ms 14.749 ms 14.869 ms]

Benchmarking hive_partitioned_agg/preserve_partition_values=false: Collecting 100 samples in
hive_partitioned_agg/preserve_partition_values=false
                        time:   [15.229 ms 15.405 ms 15.594 ms]

Are there any user-facing changes?

[gene-bordegaray]

cc: @NGA-TRAN

[NGA-TRAN]

Thanks @gene-bordegaray — impressive performance improvement! I’ll plan to review this during the first week of December. Adding a feature design description to the PR would be helpful for context.

If you identify any follow‑up work, feel free to open tickets, link this PR there, and continue working on next PRs on top of this branch.

[gene-bordegaray]

I am going to close this PR and open a new one with my refactored apporach and cleaner history

See here: #18919