-
Notifications
You must be signed in to change notification settings - Fork 991
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
multi-column non-equi join produces invalid results #2360
Comments
Quite odd. Also, if we zoom in on that row...
Somehow the inclusion of other groups in the join affects the values in this group. I think it's similar to #2275 |
I have been doing some work on a workaround for this issues, by chaining My real world case is more complex than the example above and i have been testing various combination of chaining schemes. What is interesting is that when i mix data-types on conditions. the processing is much slower than chaining those same conditions. eg:
I figured i'd note this, just in case it helps identify the source of the problem |
Thanks for the nice report. Fixed in PR. Should be merged by Matt ASAP. |
I'm trying to do self non-equi join on a date and a numeric column. The single column version of both non-equi joins produce the expected results, but when i try both columns in the on clause, i get some
very funky output.
Sample script to reproduce the problem.
The final line produces an FirstDate = "1970-01-1"
The text was updated successfully, but these errors were encountered: