Skip to content
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

[FEA] Require null_count when constructing a cudf Python column #17816

Open
mroeschke opened this issue Jan 24, 2025 · 1 comment
Open

[FEA] Require null_count when constructing a cudf Python column #17816

mroeschke opened this issue Jan 24, 2025 · 1 comment
Labels
feature request New feature or request Python Affects Python cuDF API.

Comments

@mroeschke
Copy link
Contributor

Similar to #11968, cudf Python columns should require null_count to be passed during construction. While the benefits of lazy null_count computation is lost, ideally the cudf Python column should mirror libcudf semantics as closely as possible.

xref #17760 (comment)

@vyasr
Copy link
Contributor

vyasr commented Jan 25, 2025

Also based on what we observed in libcudf there are very very few places where the lazy computation actually saves you much time. Unless you don't plan to do anything with the column you will need the null count eventually anyway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New feature or request Python Affects Python cuDF API.
Projects
Status: Todo
Development

No branches or pull requests

2 participants