-
Notifications
You must be signed in to change notification settings - Fork 40
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
Flux Queries With V1 Client Against OSS 2.x #78
Comments
Well, the As you are using a Flux query with an Org and querying a Bucket, what is missing to configure the connection as |
We recently migrated from the influx enterprise version to cloud 2 version. Almost all of our queries are written in InfluxQL, so our client is configured to use v1 as this required the least amount of changes to make the migration happen. Unfortunately some InfluxQL features aren't available anymore in the cloud 2 version so that we had to re-implement some queries with flux. To make it work with
I'm fine with explicitly passing the Btw. I noticed that cloud 2 and OSS are diverging in some parts of their API (e.g. parameterized flux queries are only supported with cloud 2). |
As the current behaviour is not really a bug but it would also be quite painful to add an option to however many function calls there are I would like to add another option: #80 This should allow you to keep your code as is and only require |
Hey, thanks for the effort. I just gave your branch a spin but I ran into another problem with that: We are still relying on the DBRP mapping for backwards compatibility. If I configure the client with We could add another option for that but I'm not sure if I'm a fan of that idea 😅 |
The
org
is not added to the URL parameters when using a connection configured for v1 against an InfluxDB OSS 2.x.The API documentation states that either one of those is required in the query parameters.
I'm currently working on a fix.
The text was updated successfully, but these errors were encountered: