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:
Flux queries corresponding to influxql meta-queries (show tag keys, show tag values) should support filtering by _field (the field name) efficiently. There is a performance improvement for these filters implemented in 2.x OSS that we would like to be back ported to 1.x.
Note the implementation in that PR would need to change somewhat to be compatible with InfluxDB Enterprise. Ideally the influxql backend could be shared by both flux and influxql - this would require improvements to the influxql metaquery backend.
Current behavior:
Flux queries over influxdb tag keys and values that otherwise could be pushed down to the storage engine and made more efficient will instead use less-efficient strategies when the filter() contains _field.
Desired behavior:
We would like these queries to be maximally efficient
Alternatives considered:
N/A.
Use case:
Filtering tag keys and values by which field keys they show up with.
The text was updated successfully, but these errors were encountered:
lesam
changed the title
Flux meta-queries (keys(), tag groups) should allow push-downs of filters including _field in the predicate
Flux queries of influxdb tags (keys(), tag groups) should allow push-downs of filters including _field in the predicate
Apr 8, 2021
Proposal:
Flux queries corresponding to influxql meta-queries (
show tag keys
,show tag values
) should support filtering by_field
(the field name) efficiently. There is a performance improvement for these filters implemented in 2.x OSS that we would like to be back ported to 1.x.See the tests proposed in https://github.com/influxdata/influxdb/pull/21160/files for how this feature would look.
Note the implementation in that PR would need to change somewhat to be compatible with InfluxDB Enterprise. Ideally the influxql backend could be shared by both flux and influxql - this would require improvements to the influxql metaquery backend.
Current behavior:
Flux queries over influxdb tag keys and values that otherwise could be pushed down to the storage engine and made more efficient will instead use less-efficient strategies when the filter() contains
_field
.Desired behavior:
We would like these queries to be maximally efficient
Alternatives considered:
N/A.
Use case:
Filtering tag keys and values by which field keys they show up with.
The text was updated successfully, but these errors were encountered: