-
Notifications
You must be signed in to change notification settings - Fork 103
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
init influxdb2 support #47
base: master
Are you sure you want to change the base?
Conversation
@David00 Just looking for your thoughts on things that need to be changed |
Hi BCNelson, thanks for putting this together! I haven't tested it yet, but after reviewing it, the only thing I would want to have changed is the default DB version to 1 in config.py. This is mainly so that I don't have to go redo my documentation and test all the dashboards. I was not familiar with Are there any benefits that moving to Influx 2.0 would bring my project? I understand they're moving to their Flux query language in 2.0 but I haven't used it. |
@David00 Leaving out the version number is the same as setting it to version 1. I believe that is even better backwards compatibility. |
As far as I can tell there are not many benefits to version 2 of influxdb. I'm not an influxdb expert by any means. My motivation was to be able to use a central db server and one of my other services needed v2. |
Works like a charm! Thanks |
A drawback to influxdb 2 is it drops 32-bit arm support, so it won't work on <= Pi 3 |
@kizniche this is just the influx client witch does support 32bit arm. It is just a http api. I don't think that there is a need to have the influxdb 2 server on the pi as I did this to have a central influx server. |
I exclusively use the influxdb server on Raspberry Pis. I'm just mentioning it because it's an important point to consider for the software component of hardware designed for a Raspberry Pi, since it would be excluding support for the vast majority of Pis that currently exist. Edit: if this is only expanding the ability to use influxdb2 in addition to influxdb1, then that sounds like a good addition. I just wanted to mention the current need for influxdb1 for most Pis. It appears to be a misunderstanding on my part that this PR may have affected the ability to use influxdb1. |
This is the Initial support for version 2 of the influxdb protocol. it is mostly useful for remote instances of influxdb that need to be on version 2.