feat: add maintain_order argument to list.unique#3697
Open
Shaan-alpha wants to merge 1 commit into
Open
Conversation
Expose Polars' `maintain_order` parameter on `Expr.list.unique` and `Series.list.unique`. For the Polars backend it is forwarded natively; the other backends do not guarantee the order of unique values, so they raise `NotImplementedError` when `maintain_order=True` (mirroring how Ibis handles descending `list.sort`).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
Adds a
maintain_orderkeyword argument toExpr.list.uniqueandSeries.list.unique, matching the Polars API.maintain_orderonlist.unique).NotImplementedErrorwhenmaintain_order=True. The default (maintain_order=False) behaviour is unchanged. This mirrors how the project already handles partial support elsewhere (e.g. Ibis raising for descendinglist.sort).not_implementedlist.unique, so they are unaffected.Happy to extend native order-preserving support to the SQL backends in a follow-up if you'd prefer that over raising.
What type of PR is this? (check all applicable)
Related issues
maintain_orderargument in{Expr, Series}.list.unique#3649Checklist