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.
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
add filter and filter! to GroupedDataFrame #2279
add filter and filter! to GroupedDataFrame #2279
Changes from 3 commits
1268ba0
2fd0bff
ebe7d82
16a603e
b1195f7
1123ff8
913d43e
d480b1f
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Do we have any other in-place functions on
GroupedDataFrame
already, apart fromselect!
andtransform!
? I'm asking because for consistency with the two latter, it would make sense forfilter!
to drop rows fromparent(gdf)
. Though that could be a unexpected. We need a general policy on this, which could also apply to in-place oeprations onSubDataFrame
.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.
This is a good question (actually I initially considered to add
filter
only for these reasons). It applies both tofilter
andfilter!
. I have not thought about it because what I proposed was most natural.So the considerations are:
GroupedDataFrame
in-placeSubDataFrame
schema in-place (of course we allow mutating the data, but not schema)select!
andtransform!
work only for someGroupedDataFrames
(ones that have no groups dropped) and they guarantee to retain row count in the parent; also it is in general expected (and documented) that they mutate the parent as they define new columns in generalfilter!
andfilter
can work on an already "subsetted"GroupDataFrame
so then it would be confusing what should happen with groups that are already not present.filter(predicate, collecion)
does the same ascollection[predicate.(collection)]
, which does not mutate the parent ofcollection
if it is present.All in all I think it is better to keep what we have.