InfluxDB2.0 Upgrade and In(-Flux) Language

[NielsKorschinsky]

Partly Copied from internal git.

InfluxQL does not allow Joins - only in a very limited pattern:

Multiple SELECT statements in a subquery

InfluxQL supports multiple nested subqueries per main query:

SELECT_clause FROM ( SELECT_clause FROM ( SELECT_statement ) [...] ) [...]
                     ------------------   ----------------
                         Subquery 1          Subquery 2

InfluxQL does not support multiple SELECT statements per subquery:

SELECT_clause FROM (SELECT_statement; SELECT_statement) [...]

The system returns a parsing error if a subquery includes multiple SELECT statements.

To allow more usefull joins it would be neccecary to use the build in FLUX-Language. This one is implemented since InfluxDB1.7.4.

In the wiki it is said, that it is possible to use InfluxQL and Flux on the same Database at once.
It might be good to consider, to upgrade to InfluxDB 2.0 meanwhile, since this does support both flux and InfluxQL, leaving us with a newer version while our old Code will still work with only minor edits.
Please check out this InfluxDB2.0 Release Roadmap

Flux would mostly affect grafana, the python code could stay like it is until we rework it to support FLUX-Language.
This would require a rework of the whole influx folder and be an other issue at this time.

possibly outdated information following:

This plugin allows to manage a influxdb-datasource as flux-source. You one database saved as both Flux and InfluxQL-Souce (individually).

Links:

• Flux vs InfluxQL
• Join data with flux

[NielsKorschinsky]

The upgrade to Influx 2.* is of high priority.
The non-enterprise version of InfluxDB 1.* did not receive security updates for a longer period.
An easier upgrade is possible using Mappings, see SPMon branch.
However, it might be more reasonable to switch to Flux, though this will require a rewrite of the whole Influx directory and associated queries.