You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Proposal:
According to this document. The influxdb still supports the influx Query Language (QL).
Current behavior:
Currently using a query which has QL syntax ends with error: error @1:1-1:7: undefined identifier select
Desired behavior:
There is a way to run influx Query Language with this client. If this is not supported, it should be written explicitly in the documentation that this feature is not supported.
Alternatives considered:
Rewriting all the QL-queries into flux which cause additional effort
Writing own client to support the Query Language
Use case:
Existing application used in production was implemented using Query Language syntax. After upgrading the database from version 1.x to the newest 2.x it is not possible to use the client with queries written in Query Language
The text was updated successfully, but these errors were encountered:
Proposal:
According to this document. The influxdb still supports the influx Query Language (QL).
Current behavior:
Currently using a query which has QL syntax ends with error:
error @1:1-1:7: undefined identifier select
Desired behavior:
There is a way to run influx Query Language with this client. If this is not supported, it should be written explicitly in the documentation that this feature is not supported.
Alternatives considered:
Use case:
Existing application used in production was implemented using Query Language syntax. After upgrading the database from version 1.x to the newest 2.x it is not possible to use the client with queries written in Query Language
The text was updated successfully, but these errors were encountered: