kosiew opened a new pull request, #13995:
URL: https://github.com/apache/datafusion/pull/13995
## Which issue does this PR close?
<!--
We generally require a GitHub issue to be filed for all bug fixes and
enhancements and this helps us generate change logs for our releases. You can
link an issue to this PR using the GitHub syntax. For example `Closes #123`
indicates that this PR will close issue #123.
-->
Closes #13949.
## Rationale for this change
<!--
Why are you proposing this change? If this is already explained clearly in
the issue then this section is not needed.
Explaining clearly why changes are proposed helps reviewers understand your
changes and offer better suggestions for fixes.
-->
When an aggregation operator spills intermediate (partial) state to disk, it
needs a schema that includes both the group-by columns and partial-aggregator
columns (e.g., partial sums, counts, etc.). Previously, the code used the
original input schema for spilling, which does not match the additional columns
representing aggregator states. As a result, reading back the spilled data
caused a mismatch error:
```
ArrowError(InvalidArgumentError(
"number of columns(3) must match number of fields(2) in schema"
))
```
This PR addresses that by introducing a partial aggregation schema that
combines group columns and aggregator state columns, ensuring consistency when
spilling and later reading the spilled data.
## What changes are included in this PR?
<!--
There is no need to duplicate the description in the issue here but it is
sometimes worth providing a summary of the individual changes in this PR.
-->
1. A new helper function, build_partial_agg_schema(), creates a partial
schema by merging:
- Group-by fields
- Each aggregator’s internal “state fields”
2. The aggregate operator is updated to use this partial schema when
spilling or merging spilled data rather than the original (input) schema, which
fixes the column mismatch error.
## Are these changes tested?
<!--
We typically require tests for all PRs in order to:
1. Prevent the code from being accidentally broken by subsequent changes
2. Serve as another way to document the expected behavior of the code
If tests are not included in your PR, please explain why (for example, are
they covered by existing tests)?
-->
Yes
## Are there any user-facing changes?
<!--
If there are user-facing changes then we may require documentation to be
updated before approving the PR.
-->
No
<!--
If there are any breaking changes to public APIs, please add the `api
change` label.
-->
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org
For additional commands, e-mail: github-h...@datafusion.apache.org
