Hello,
InfluxDB3 alpha (then) beta user here. I have just read the official statement about the GA of InfluxDB3 (Core/Enterprise), also pinned in this community forum.
I have some questions:
I cannot understand the procedure to get a Free Tier for Home Users license. It looks like it has been disclosured no where;
For users coming from Beta version, can the Beta installation be converted in the “GA version” without a new installation?
Finally, I would like to know if InfluxDB V2 is officially considered dead. Unfortunately, after reading the statement about the Free Tier for Home users (no high-availability, only two cores, Flux language abandoned…) I am still very uncertain about the upgrade.
To install the free tier you can simply install the new Enterprise GA software and start the server. It will prompt you for the type of license you want where you can select Home Use.
The Beta can’t be converted without a license change, but can continue to be used for the duration of the Beta license, which will go into mid-May. We encourage you to take that time though to convert to the At-Home license.
v2 continues to remain supported with security/bug fix updates, and has no EOL planned currently. We do encourage users to move to InfluxDB 3, however, as we’ll be continuing to develop an extensive feature set on our roadmap.
For Flux, we’re certainly disappointed we couldn’t bring it forward, however the Processing Engine is able to deliver all-and-more than what Flux could do on its own. We intend to invest heavily there to ensure it’s a great and seamless experience.
Hello, thanks for your reply but I do not feel so encouraged to move towards V3, no matter if it will be the V3 Core or the V3 Home Use, based on very strict limitations on both products you introduced.
I’m sure this has been mentioned, but my biggest frustration with regards to Flux is that it was promoted as being the future of Influx. I spent a lot of time converting my old IQL into Flux (both for scheduled tasks and my dashboards). It’s very disheartening to learn that I will eventually have to convert everything back to IQL. That’s going to prevent me from moving to v3 for a long time, I suspect.
@tkohhh
Same situation as you.
Much time spent on learning Flux, after working with InfluxQL and now… pufffff. By the way, we should get back to a language way far less powerful than Flux (InfluxQL) and with a version having many a long list of limitations.
That makes so much sense. You are not alone. I would also be frustrated. I’m here to help with that if you need. However using Python for tasks I believe will be a lot easier than Flux. But yah the whiplash is real.
The real power with v3 is the embedded python processing engine. This was in response to realizing that we’d never be able to provide all the functionality that users want with Flux. And yes the parquet limitations are frustrating as well. Certainly if you’re a hobbyist that has minimal data processing requirements and a requirement to query back long data v2 is the better option for you, this is evident. If you’re working with processing shorter term data, want integrations with data lakes for long term storage, and have heavier data analysis or processing tasks then v3 is the better alternative. But yes a lot of our v2 users were iot hobbyist and v3 is disappointing. I am here to help with query conversion or creating any python plugins.
