1.x and 2.x are, which is why 3.x reinvents the product around standard tech (true SQL, Apache Arrow). It's hard to ask customers to bet on a database when, to name one reason, its query language has already changed twice.

InfluxDB Founder & CTO here. We worked hard to support InfluxQL in 3.x and it supports the v1 write API. Admittedly, it will be a migration to move and we haven't yet built the tooling, but we felt it was important to get the 3.0 release out even though we don't have the migration tooling built yet. Our plan is to have that available later this year.

The 2.x to 3.x move is, admittedly, much harder. This is because of the language Flux. We haven't been able to bring that over to 3.x in a way that makes it useful. We actually built a bridge for it in our cloud offering, but our experience is that the performance isn't good enough to be acceptable for customers wanting to upgrade. If they want to make the move, adopting SQL or InfluxQL is likely the only path.

We'll continue to develop 3.x and we'll build more migration tooling over time. I think we can build specialized tooling to help Flux users migrate over to 3.x with query translation tools, but there are more features we need to land in 3.x to enable that first.

We're committed to the technology stack (Apache Arrow & DataFusion) and the 3.x line. We have no plans for another major release. I'll be happy if we end up releasing 3.56.2 8 years from now.

I've been burned by influxdb abandoning their old versions one too many times and will never consider it for anything ever again.

Every major release of InfluxDB have been a rewrite.

While 3. looks impressive, it seems like most of the interesting features are closed source, so not a 1:1 replacement for version 1.

InfluxDB Edge is open-source, but you need to depend on InfluxDB Community which is free, but closed source, to get things like include functionality like a compactor, which will add capabilities for deletes and re-organizing files to optimize for queries on longer time ranges.

They also need to resurrect all their old 1.* Client libraries for 3.*.

I love InfluxDB, but I’m not hopeful for its future.

No joke: We've had Influx customers come to us and say that migrating from Influx 1.x to Timescale was easier than migrating from 1.x to 2.x

I use victoriametrics now, seems to be ok

Quite the opposite, InfluxDB 3 is the best time series database currently in the market in terms of features and performance.

(full disclosure, I work at InfluxData so my answer is biased).