-
Notifications
You must be signed in to change notification settings - Fork 928
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 default UNKNOWN_NULL_COUNT from cudf::column member functions #13341
Remove default UNKNOWN_NULL_COUNT from cudf::column member functions #13341
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly looks great to me! However IIUC about 50% of the changes are in the concatenate_tests.cpp file, and they don't seem relevant. That ratio is too high for me, so unless I'm misunderstanding why that's here I would like those changes split into a separate PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
/merge |
Shouldn't this have been marked BREAKING? It broke cugraph. The constructor for |
rapidsai/cudf#13341 changed the constructors for `cudf::column`. This PR updates the constructor calls to work with the latest cudf changes. Authors: - Chuck Hastings (https://github.com/ChuckHastings) Approvers: - Seunghwa Kang (https://github.com/seunghwak) URL: #3592
Yes, this should have been marked as breaking. Apologies for the oversight. @raydouglass will updating the labels now have any effect, or will we need to modify the changelog etc manually to account for this now? |
Yes, the changelog is generated from scratch each time, so if the labels are updated the next PR that merges will update the entire changelog. |
I'm not pressed about retroactively worrying about this, personally. The breaking label helps me by alerting me in the slack channel that changes might come up that might affect my development. In this case it was pretty easy to find what the culprit was (the error message clearly indicated a problem in this constructor... not too many PRs merged recently caused a change in the constructor. I don't know how the labels propagate into release documentation. If the labels have an effect on that, I suppose it would be helpful to get that tagged correctly so that it's represented in the release documentation. If that's all still manual then it's probably less important. |
Sounds good, updated the labels. |
This is the final PR for removing `UNKNOWN_NULL_COUNT` and the implicit kernel launch in the `null_count` methods of `column` and `column_view`. Depends on #13355 and #13341. Closes #11968 Authors: - Vyas Ramasubramani (https://github.com/vyasr) Approvers: - MithunR (https://github.com/mythrocks) - Nghia Truong (https://github.com/ttnghia) - Karthikeyan (https://github.com/karthikeyann) URL: #13372
Update `cudf::column` constructor args to match the changes in rapidsai/cudf#13341. Also corrects a minor issue in the docs, closes #1154. Authors: - Paul Taylor (https://github.com/trxcllnt) - Taurean Dyer (https://github.com/taureandyernv) - Bradley Dice (https://github.com/bdice) Approvers: - Michael Wang (https://github.com/isVoid) - Mark Harris (https://github.com/harrism) URL: #1151
Description
Remove the default parameters for null-mask and null-count from
cudf::column
constructors andset_null_mask
member functions.Reference #13311
Checklist