influxdata / influxdata/influxdb

Queries Not Returning All Tag Key / Value Combinations Depending on Start Time in Range

Open
#20,753 1 comment 0 reactions 0 assignees View on GitHub
area/2.x area/queries
Dominant language
Rust
Stars
31.7k
Forks
3.7k
Avg merge
13h 37m
Merged PRs (30d)
8

Description

__Steps to reproduce:__
List the minimal actions needed to reproduce the behavior.

1. Have two sets of Tag Key / Tag Value pairs, one with older data and one with newer data
2. Perform a Flux query with a timeframe that begins before the new data was entered (example in Query1.txt)
3. Perform a Flux query with a timeframe that begins within when the new data was entered (example in Query2.txt)

__Expected behavior:__

When either Flux query comes back, it should list all the Tag Key / Tag Value and Field Key combinations that contain data with timestamps that fall between the start time and the stop time

__Actual behavior:__

When the Flux query that had an older start date came back, it only showed the Tag Key / Tag Value and Field Key combinations that contained data first, the newer Tags weren't shown. When the Flux query that didn't have a start date as far back returned, it only showed the Tags that had data recently added to them. I have attached CSV files that I downloaded after performing these queries and it can easily be seen that the query with the older start date doesn't pick up the Tag Key / Tag Values that are present in the CSV from the query with the later start date.

__Environment info:__

* Running on InfluxDB 2.0 Free Version in Google Chrome

__Config:__

__Logs:__

__Performance:__

__Files:__
[outputFromQuery1.txt](https://github.com/influxdata/influxdb/files/5968224/outputFromQuery1.txt)
[Query1.txt](https://github.com/influxdata/influxdb/files/5968225/Query1.txt)
[Query2.txt](https://github.com/influxdata/influxdb/files/5968226/Query2.txt)
[outputFromQuery2.txt](https://github.com/influxdata/influxdb/files/5968232/outputFromQuery2.txt)

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the report in InfluxDB 2.0 using Query1.txt and Query2.txt, then compare their results with outputFromQuery1.txt and outputFromQuery2.txt. The fix is complete when both Flux queries return every tag key, tag value, and field key combination with data in the requested time range.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.