Implementing `groupby`
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 1
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 2
Description
Incomplete notes (most is still on paper or in headspace):
- Need to support mapped nodes in
__setitem__first, otherwisegroupbyis relatively useless. - Figure out what it means and how to handle the node mapped for grouping: When grouping a
DataArray(orDataFrame) we have a coordparambefore grouping and another coordparam(with unique param values) after. How can the be reconciled with the graph, where we can't have a node twice? Or does it work already, becauseMappedNodeincludes the index name, so there is no conflict, except that convenience features like node-name based lookup do not work anymore? - There are cases than can be drawn easily, but are hard to setup using the syntax similar to
map/reduce, combined with__setitem__to continue the graph afterreduce. Not clear if those are needed/useful, but maybe the current syntax is not sufficient.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the existing map/reduce syntax, setitem, and MappedNode handling. Clarify how mapped grouping nodes and coordinates should behave, including whether graph lookup remains usable and whether post-reduce continuation is required; done means these semantics are agreed and groupby is implemented accordingly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100