-
Notifications
You must be signed in to change notification settings - Fork 891
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
Remove scalar_to_column_view #11241
base: branch-22.08
Are you sure you want to change the base?
Remove scalar_to_column_view #11241
Conversation
What is the reason for this proposal? |
I too wonder why. I think it is to make explicit that the ownership the column-view (resulting from the @rwlee: It might be best to change the description of this PR to address what the change is, and the motivation. This is what one will see from the git log. |
This PR has been labeled |
@vyasr I think we do want to do something here and not close, but perhaps starting over with a fresh PR is warranted. There is some scalar/column logic being implemented in |
All right, I'll leave this one open for now so that we don't forget to come back to this. At some point it might be worth writing an issue with a proposal if we plan to close this issue, but for now this seems fine as documentation for the task. |
Followup to #11153 stemming from a discussion with @bdice. Opening as a workspace/discussion location to debug the issue further.
Replacing
scalar_to_column_view
withmake_column_from_scalar
causes a cuda memory error atcpp/src/binaryop/compiled/binary_ops.cuh
line 127. Both approaches should be functionally the same, the only difference being who owns the underlying single row column data.There is an additional testing issue where the results are checked regardless of validity of the scalar value. This implies that the resulting value is generated regardless of the nullability of the value -- verifying the results of undefined behavior that changes when
make_column_from_scalar
is used.