Closed tantaman closed 7 months ago
note to self: pullHistory
messages can stop at a reduce
operator if the operator has already been seeded with history.
Not sure that I like the aggregation API:
q
.select('status')
.groupBy('status')
.array('assignee')
.min('created');
maybe it should be:
q
.select('status', agg.array('assignee'), agg.min('created'))
.groupBy('status')
Another strawman:
q
.select('status').
.agg('array', 'assignee')
.agg('min', 'created')
But I think I prefer the first suggested API.
updated the API to allow putting aggregate calls in select
:
q
.select(
'status',
agg.array('assignee'),
agg.min('created', 'minCreated'),
agg.max('created', 'maxCreated'),
)
All aggregate functions can be modeled as
reduce
This adds a
reduce
operator so we can do:This targets SQL behavior for group-by.