Closed justinkalland closed 3 years ago
I think it would be great to support Influx 2.0 with this project. Fewer nodes for supporting Influx would be better I think; at least make it easier to find the node.
I'd be glad for your help if you're interested. Maybe we can introduce the new client as a dependency and add a version configuration? What do you think? As you've probably seen already, the code is pretty simple.
On Sat., Oct. 12, 2019, 10:36 p.m. Justin Kalland, notifications@github.com wrote:
Aloha, thanks for your node contribution, I use it a lot! I am migrating some systems to Influx 2 and currently I am just using raw queries in Node-RED to interact with InfluxDB2 API. I was considering making a new set of contrib nodes specifically for InfluxDB 2, but wanted to get your take on it first. Do you think a new project is justified? Or perhaps you would like to roll support for V2 into this project? The official node client is out and works great.
Here are some references:
- INfluxDB 2.0 Overview https://www.influxdata.com/products/influxdb-overview/influxdb-2-0/
- InfluxDB v2.0 Documentation https://v2.docs.influxdata.com/v2.0/
- Influx API Service (full API Docs for v2) https://v2.docs.influxdata.com/v2.0/api/
- Official InfluxDB 2.0 JavaScript client https://github.com/influxdata/influxdb-client-js
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/mblackstock/node-red-contrib-influxdb/issues/50?email_source=notifications&email_token=AAFMY6CRP4KUKCVNHXEUGI3QOKXVTA5CNFSM4JAFSWZ2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HRNGEOQ, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFMY6DXOBMVIN3QL6RNZSDQOKXVTANCNFSM4JAFSWZQ .
I think adding support into this set of nodes is a great idea, but many choices will have to be made. I started to tinker with it as a version setting in the database config node. Interacting with v2 can be very different, such as the new query language Flux. It also seems there is naming differences in Influx 2, such as "buckets".
I see. It might be good to create an additional node or two to support the new features. I'll have a look. If you have any specific ideas, let me know.
On Sun., Oct. 13, 2019, 7:31 p.m. Justin Kalland, notifications@github.com wrote:
I think adding support into this set of nodes is a great idea, but many choices will have to be made. I started to tinker with it as a version setting in the database config node. Interacting with v2 can be very different, such as the new query language Flux https://www.influxdata.com/blog/influxdb-2-0-alpha-release-and-the-road-ahead/. It also seems there is language differences in Influx 2, such as "buckets".
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/mblackstock/node-red-contrib-influxdb/issues/50?email_source=notifications&email_token=AAFMY6CRWZVJGRFIUJ7LXGDQOPKZPA5CNFSM4JAFSWZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBDGX4I#issuecomment-541486065, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFMY6GA62WVJQW25LG5X4LQOPKZPANCNFSM4JAFSWZQ .
Hello, is there any progress or roadmap for this feature?
I am using new flux scripting lang and it is very powerful.
Having this feature would very much appreciated.
Hi @mblackstock, some nodes were added for supporting InfluxDB 2.0 and InfluxDB 1.8 Flux using the 2.0 compatibility API. A Pull request was created here: #63.
Aloha, thanks for your node contribution, I use it a lot! I am migrating some systems to Influx 2 and currently I am just using raw queries in Node-RED to interact with InfluxDB2 API. I was considering making a new set of contrib nodes specifically for InfluxDB 2, but wanted to get your take on it first. Do you think a new project is justified? Or perhaps you would like to roll support for V2 into this project? The official node client is out and works great.
Here are some references: