You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Different group_by result due to doing joins with by_chund_id #356
The problem was in previous steps I had done some joins with the option merge_by_chunk_id = TRUE and the result of those joins were different from the ones when using data frames. I still cannot distinguish between these these two ways of joining the data. why do we set merge_by_chunk_id to TRUE while the generated data isn't what we expect. anyway I set merge_by_chunk_id to FALSE and the issue seemed to be resolved but at the end I got an error for the stack size limit!
Activity
xiaodaigh commentedon Sep 16, 2021
That's not good. I will see if I can reproduce it. Can you tell me the types of col1 col2 etc? How many unique values in each?
SMousavi90 commentedon Sep 16, 2021
The problem was in previous steps I had done some joins with the option merge_by_chunk_id = TRUE and the result of those joins were different from the ones when using data frames. I still cannot distinguish between these these two ways of joining the data. why do we set merge_by_chunk_id to TRUE while the generated data isn't what we expect. anyway I set merge_by_chunk_id to FALSE and the issue seemed to be resolved but at the end I got an error for the stack size limit!
xiaodaigh commentedon Sep 18, 2021
I see. A proper article on how join work is long overdue.
[-]Different group_by result[/-][+]Different group_by result due to doing joins with `by_chund_id`[/+]