DRILL-8545: Disable HashAgg for collect_to_list_varchar due to ordering requirements

[rymarm]

DRILL-8545: COLLECT_TO_LIST_VARCHAR function returns incorrect result when Hash Aggregator operator used

Description

Root cause

The collect_to_list_varchar function is incompatible with the Hash Aggregator because the aggregator processes data in a non-sequential manner, while the underlying ValueVector framework requires sequential writes for variable-length data. Furthermore, the Drill UDF framework lacks a straightforward mechanism to buffer these values internally before flushing them to the output vector, making it impossible to reorder them on the fly during the aggregation phase.
Solution

Solution

To ensure data integrity and prevent index out-of-bounds exceptions, I have modified the Hash Aggregator physical planning rule. The planner will now explicitly disallow the Hash Aggregator if a collect_to_list_varchar call is detected in the aggregate expression. This forces the optimizer to fall back to the Streaming Aggregator, which provides the necessary ordered input.

Documentation

No changes.

Testing

Updated the available unit test cases so they cover the mentioned problem.

[cgivre]

@rymarm Thank you for this enhancement. I'm fine with the changes, but I have a question before I approve. If a Drill cluster is configured with HashAgg enabled, and a user executes a query with collect_to_list_varchar, will Drill fall back to StreamAgg or will Drill throw an error? I was a little confused by the unit tests.

[rymarm]

@cgivre Hi Charles!

If a Drill cluster is configured with HashAgg enabled, and a user executes a query with collect_to_list_varchar, will Drill fall back to StreamAgg or will Drill throw an error?

Yes, definitely. If a Drill cluster is configured with HashAgg enabled and StreamAgg is enabled either (by default, both HashAgg and StreamAgg operators are enabled), Drill will simply fallback to the StreamAgg operator. Otherwise, if HashAgg is enabled and StreamAgg is DISABLED - Drill will throw an exception CannotPlanException, because Drill has only 2 aggregation operator implementations at all, and in this case, one is not acceptable, and another one is disabled.

[cgivre]

+1 LGTM
Thanks @rymarm for this!