Nathaniel Cook

I say lets wait for the type inference work on this one.

Adding some more details: Another similar implementation of aggregate helper function ``` aggregate = (aggregates, table= { tables = aggregates |> map(fn: (k,v) => { return { [k]: table |>...

Adding example of how to call aggregate: ``` from(db:"foo") |> range(...) |> filter(...) // Produces a table with columns sum_value, mean_value, and count_value |> aggregate(aggregates:{sum,mean,count}) ```

No the request and design here goes beyond what `aggregateWindow` can offer.

This can be fixed by implementing the proposal in #1032

@tennox @danhallin Thanks for the interest in this issue and for sharing your workarounds. This is clearly a first class feature Flux needs. We have tried to tackle this issue...

@OrangeFlag That is an interesting idea. I saw you closed your PR for Elastic source https://github.com/influxdata/flux/pull/1165. I apologize for not getting to that sooner. Is that something you still want...

@OrangeFlag Glad to hear it. I am traveling next week so I won't be able to take a look for a while yet, but yes we will help out with...

@jben94 Glad to see that the `intervals` function would be useful for you. It is not currently implemented. You can follow this issue https://github.com/influxdata/flux/issues/407 for our progress.

Why does this need to be specific to influxdb-relay? Can't a trusted certificate be added to the system as a whole?