Christopher M. Wolff

I recently made some changes to how we propagate errors from the Flux controller. As a result the error formatting in the platform REPL is a little more wonky than...

Some discussion on Slack with @aanthony1243 about how to get better tracing of Flux execution: we could add a planner option that would inject `yield` nodes in between plan nodes...

I filed #1439 that describes a possible way to do this.

Some notes from Slack discussion about how to parse line protocol: - There are a surprising number of edge cases in parsing line protocol, mostly related to escaping in string...

@aanthony1243 I like this proposal. One thing to note is that `Source` is defined in the `execute` package which already imports `plan`. So the `plan` package (as it is now...

I think it would be best to have 5 built-in rules for each of the 5 kinds of things we can push down into sources. The logic for any one...

I totally agree with this. I've been thinking that the DAG-ness of our plans also broadens the search space, since it might sometimes be beneficial to duplicate operations if we...

Suppose we have a query like this one, ``` thirdParty.from(...) |> filter(...) |> group(...) |> max() |> filter(...) // filter the result of the aggregate operations e.g., _value > 100...