We’re not yet sure how to support Flux in 3.0. We built a compatibility layer in our Cloud product that has a Flux process (written in Go) that communicates via gRPC to a 3.0 query engine. We’ve found through testing that it doesn’t perform very well (users see things that used to work that now time out) and there are a number of hidden bugs as the protocol is very different from how the underlying 3.0 query engine works.
We were able to bring InfluxQL support in natively because of its similarity to SQL, which is what our new query engine supports by default. That effort took a year and involved writing an InfluxQL parser in Rust that yielded an AST that could then be converted to DataFusion Logical Plans (SQL query plans), and then we implemented new features in the SQL engine to support some of the things that InfluxQL supported that the SQL engine didn’t have built in.
We don’t yet have the story for what we can do with Flux. It’s significantly more complex than InfluxQL as it’s an entire scripting engine. We’ll continue to support our Cloud2 platform and Flux on it for quite some time (no set future date at this point) as we do more work to figure out what a decent transition can look like.
