Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upmulti-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"
