-
Notifications
You must be signed in to change notification settings - Fork 149
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
InfluxDB 2.x support #14
Comments
InfluxDB Enterprise 2.x has not been released yet, and the next plan for InfluxDB Cluster is to adapt to InfluxDB Enterprise 1.9.x and InfluxDB Enterprise 1.10.x |
hi @chengshiwen , I understand what you mean, but I believe that there will never be a public release of InfluxDB cluster 2.x. |
p.s.: I'm an enterprise customer and I could try to raise it with them once again, but I expect them to be slippery and evasive as usual. |
Maybe so. I will release v1.8.10-c1.2.0 as soon as next two months to support anti-entropy feature. Then I will try to figure out the clustering mechanism of InfluxDB Cloud, which requires some work. |
hopefully v2 compatible version is not too far away will there be any integrated auto incremental backup scripts ? |
Yes. InfluxDB Cluster v1.8.10-c1.2.0 will support (incremental) backup and restore like the official document:
I will try to give a solution on the new minor version v1.8.10-c1.2.0, which will be released next one or two months. |
ok thanks , I will give this a spin , I have a docker lxc running to run this docker container inside off anyhow , hopefully Home Assistant will not complain about downgrading the influxdb version |
when will v1.8.10-c1.2.0 be release ? |
expect! |
Same me, waiting for influxdb 2 |
is the plan is stop for open source? @chengshiwen |
The cluster plan for InfluxDB 1.x will continue to be open source and maintained. There is no plan for InfluxDB 2.x yet, so I will probably consider the cluster open source solution for 3.x directly. |
Proposal: is there any plan to support InfluxDB 2.x ?
The text was updated successfully, but these errors were encountered: