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
Dear InfluxDB Team, When we enclose the time field in parentheses within a predicate expression, in the following query, the actual query range for time should be greater than the timestamp 1741024000000000000. However, data with a timestamp of 1641024000000000000 is still being retrieved, indicating a logical error.
Steps to reproduce
In the latest version of InfluxDB, if we have an organization named "organization", we can use the Influx client to execute the following commands to create a bucket and write the specified data into that bucket.
Dear InfluxDB Team, When we enclose the
time
field in parentheses within a predicate expression, in the following query, the actual query range fortime
should be greater than the timestamp1741024000000000000
. However, data with a timestamp of1641024000000000000
is still being retrieved, indicating a logical error.Steps to reproduce
In the latest version of InfluxDB, if we have an organization named "organization", we can use the Influx client to execute the following commands to create a bucket and write the specified data into that bucket.
Next, we use the
influx v1 shell
command to enter the Influx shell backend and execute the following query statement:Expected behaviour
Query 1 returned result set: empty set
Actual behaviour
Query 1 returned result set: 1
Environment info
Influx CLI dev (git: a79a2a1b825867421d320428538f76a4c90aa34c) build_date: 2024-04-16T14:34:32Z
InfluxDB OSS v2.7.11 (git: fbf5d4a)
Linux 5.15.0-94-generic x86_64
The text was updated successfully, but these errors were encountered: