Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect input schema when preparing result expressions for HashAggregation #502

Closed
viirya opened this issue Jun 1, 2024 · 0 comments · Fixed by #501
Closed

Incorrect input schema when preparing result expressions for HashAggregation #502

viirya opened this issue Jun 1, 2024 · 0 comments · Fixed by #501
Labels
bug Something isn't working

Comments

@viirya
Copy link
Member

viirya commented Jun 1, 2024

Describe the bug

If there are result expressions for Spark HashAggregation, we prepare these physical expressions to add an additional DataFusion ProjectionExec on top of AggregateExec.

Currently we incorrectly use AggregateExec's child schema as input schema to prepare these physical expressions. It causes some test failures in #403 as latest DataFusion adds additional check for that in apache/datafusion#10088.

Steps to reproduce

No response

Expected behavior

No response

Additional context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
1 participant