Use drop_duplicates instead of unique for cudf's pandas compatibility mode #5639
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.
In pandas,
Series.unique
returns a numpy array (for non-extension types) whileSeries.drop_duplicates
returns aSeries
. The two results should otherwise contain the same set of values. In cudf, historically both methods returned aSeries
, and at these stages in cuml's pipeline it knows that it is working with cudf objects. However, if cudf has pandas compatibility mode enabled, thenunique
will return an array to match pandas behavior. In this scenario, the method chaining no longer works because cupy is calling methods on the result ofunique
assuming that it will be aSeries
. To fix this, cuml needs to calldrop_duplicates
instead.