influxdata / influxdata/influxdb
Optimize `keep()/drop() |> aggregateWindow` Flux Queries
Open
area/2.x
area/flux
area/performance
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
Flux queries involving `keep() |> aggregateWindow` or `drop() |> aggregateWindow` are slower than their InfluxQL equivalents. This issue is to optimize the Flux queries to be on par with InfluxQL.
For `keep`, reference the community issue here: https://github.com/influxdata/influxdb/issues/18088
For `drop`, see: https://github.com/influxdata/influxdb-comparisons/pull/198
Contributor guide
Research direction
No source files or tests are named in the issue. Start by reviewing community issue 18088 for keep() and influxdb-comparisons pull request 198 for drop(); done means Flux queries using keep() or drop() before aggregateWindow perform on par with their InfluxQL equivalents.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- databases, performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100