You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 29, 2021. It is now read-only.
In order to implement aggregations, we need to be able to group data. Like joins, the task of grouping probably belongs upstream, but we should be able to define how to group data.
The LazyFrame might need some state (whether it's grouped or not) to prevent 'normal' calculations when it's in a grouped state. I don't want to implement a GroupedLazyFrame because we rely on mutating the &mut LazyFrame to add on computations.
An aggregation should ideally take in multiple aggregations.
A grouping should take in multiple columns, with columns that aren't grouped or aggregated, getting dropped.
The text was updated successfully, but these errors were encountered:
Data is grouped in order to be aggregated, so perhaps it might be better not to create an intermediate grouped data structure, but instead take the grouping and aggregations at the same time.
The grouping can be Vec<&str>, but aggregates should be more expressive, as either functions that implement some aggregation trait, or an enum if we support a finite list of aggregations.
In order to implement aggregations, we need to be able to group data. Like joins, the task of grouping probably belongs upstream, but we should be able to define how to group data.
The
LazyFrame
might need some state (whether it's grouped or not) to prevent 'normal' calculations when it's in a grouped state. I don't want to implement aGroupedLazyFrame
because we rely on mutating the&mut LazyFrame
to add on computations.An aggregation should ideally take in multiple aggregations.
A grouping should take in multiple columns, with columns that aren't grouped or aggregated, getting dropped.
The text was updated successfully, but these errors were encountered: