-
Notifications
You must be signed in to change notification settings - Fork 904
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
Support equally comparing two different tables in the newly experimental row comparator #10667
Support equally comparing two different tables in the newly experimental row comparator #10667
Conversation
@jrhemstad @devavret The new equality comparator seems to be incorrect for sliced input. I still didn't figure out what's wrong. If you uncover anything, please let me know. |
This comment was marked as off-topic.
This comment was marked as off-topic.
@bdice If you are working on similar thing, please apply this patch: https://github.com/rapidsai/cudf/pull/10667/files#diff-0743b70282a92785dee8e55adc4099f501b4ed6c20c21e39fe187b2f4f0664a0L560-R562. It is fixing the bug when the input column is sliced. |
In addition, I'm still not sure if this (https://github.com/rapidsai/cudf/pull/10667/files#diff-0743b70282a92785dee8e55adc4099f501b4ed6c20c21e39fe187b2f4f0664a0R573-R574) also needs to be fixed by the same way. This needs to be tested too. |
This reverts commit a8a2788.
The new row comparator (#10164) only added a
self_comparator
utility to compare rows of the same table. This PR addsequality::table_comparator
that allows equally comparing rows from different tables. Immediate usage of such comparator is for linearly searching a struct scalar in a structs column.In addition, it also fixes the comparator that produces wrong results when the input is sliced.
This PR is required for #10548 and #10656.