Echoing Phil_Lundeen’s perspective, our company has put a lot of resources into adopting and embracing flux even though we have legacy servers chugging along with 1.8’s influxql. This we did because influxdata org indicated through various channels that flux was “getting there”.
I understand hard decisions are hard by definition.
That said, what would be a path forward to allow for a community lift of getting flux to be a first-class language that supports FlightSQL and isn’t completely binned? There is a possibility of outside corporate effort being dedicated to this cause (just like it is done in other OSS projects like postgresql and linux).
