-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Regression: Panic when running complex query on 0.20.17 backtrace included #15375
Comments
Looks like it's this line of code https://github.com/pola-rs/polars/blob/main/crates/polars-plan/src/logical_plan/optimizer/predicate_pushdown/mod.rs#L357C43-L357C44 Might be to do with hive partitioning |
Can confirm that turning off my hive partitioning prevents this from occurring. |
My complex query also fails with a missing column near the end of execution of the query (that previously worked in 0.20.16). I'll try to produce a MRE for that, might be hard to. |
Also found that the missing column regression still occurs with optimization turned entirely off. |
Thansk for the report, but this will be hard to fix without a reproducible example. |
I tried to produce a repro for both issues, unfortunately couldn't get them working :( I can pin down the exact commits that caused issues though if that helps? |
So the second bug (where I got a missing column) seems to come from this, i'm guessing at some point aliasing isn't carried through properly. I couldn't reproduce it with something small though... I changed my The first bug with the panic seems to occur from this @ritchie46 I could only solve this by disabling hive partitioning. |
This is fixed now right? After #15381 |
Yep! |
Checks
Reproducible example
Can't share my code unfortunately
Log output
Issue description
When running a complex query with several joins/filters/computations I get a panic
Expected behavior
Shouldn't panic
Installed versions
The text was updated successfully, but these errors were encountered: