Drop unsupported method argument from nunique and distinct_count. #10411
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The APIs
DataFrame.nunique
,Series.nunique
, andColumnBase.distinct_count
have amethod
argument. The pandas API fornunique
does not have amethod
argument. Thismethod
argument was meant to distinguish distinct counts computed by sort/hash approaches, but there are two issues: only"sort"
is supported as an input value, and the algorithm in libcudf actually uses a hash-based approach. To resolve this inconsistency and align with the pandas API, I have removed themethod
parameter fromDataFrame.nunique
,Series.nunique
, andColumnBase.distinct_count
.This is a breaking change but I don't think a deprecation is needed. The
nunique
feature was added in 22.04 via #10077, so it has not yet been released. The internal changes todistinct_count
can be made without a deprecation.