-
Notifications
You must be signed in to change notification settings - Fork 14
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
CoalescePartitionsExec requires at least one input partition
when aggregating empty tables on single-core machines
#186
Comments
mildbyte
changed the title
Oct 31, 2022
CoalescePartitionsExec requires at least one input partition
when aggregating empty tables on Fly.ioCoalescePartitionsExec requires at least one input partition
when aggregating empty tables
Doesn't just happen on Fly.io, I had an older debug version in my Docker, could be a regression in a recent DF. |
mildbyte
changed the title
Nov 2, 2022
CoalescePartitionsExec requires at least one input partition
when aggregating empty tablesCoalescePartitionsExec requires at least one input partition
when aggregating empty tables on single-core machines
It looks like it's because of the number of cores allocated (becomes
The physical plan for single-core is missing |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This only happens on Fly.io (I think I tested this with the same Docker image locally and didn't get the issue):
Local Docker (TODO: quadruple-check it's definitely the same Docker image as the one on Fly):
The text was updated successfully, but these errors were encountered: