-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
fix: Validate/coerce types for comparisons within join_where predicates #21049
fix: Validate/coerce types for comparisons within join_where predicates #21049
Conversation
a7df6fe
to
d216e4a
Compare
d216e4a
to
3693a97
Compare
}, | ||
_ => true, | ||
}); | ||
polars_ensure!( valid, InvalidOperation: "'join_where' predicate only refers to columns from a single table") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
check refactored to process_join_where_predicate()
below
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #21049 +/- ##
==========================================
+ Coverage 79.19% 79.27% +0.07%
==========================================
Files 1585 1585
Lines 226009 226132 +123
Branches 2592 2592
==========================================
+ Hits 178985 179257 +272
+ Misses 46429 46280 -149
Partials 595 595 ☔ View full report in Codecov by Sentry. |
@nameexhaustion I also got this python error? Any idea what it is? |
I will make a PR to fix |
|
Adds a type validation / coercion step to join_where predicates. This ensures comparison expressions within the predicates have compatible dtypes (matching, or have a lossless supertype).
Drive-by
is_comparison()
function tois_comparison_or_bitwise()
to better reflect what it matches