We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When querying data in the v1 shell the timestanps are wrong:
SHOW RETENTION POLICIES ON my_db name,tags,name,duration,shardGroupDuration,replicaN,default ,,autogen,0s,168h0m0s,replicaN,true
influx v1 shell
use "my_db"
precision ns
SELECT time,temp FROM "heating" WHERE temp=0
the returned timestamps should be correct and in nanosecond precision
the returned timestamps are incorrect example:
curl --get 'http://my_server:8086/query' --header 'Authorization: Token <my token>' --header 'Accept: application/csv' --header 'Content-type: application/json' --data-urlencode 'orgID=m<_org' --data-urlencode 'db=my_db' --data-urlencode 'epoch=ns' --data-urlencode 'q=SELECT time,temp FROM heating WHERE temp = 0'
the corresponding entry is: heating,,1735325299900396750,0
heating,,1735325299900396750,0
DELETE FROM "heating" WHERE time = 1735325299900396800
DELETE FROM "heating" WHERE time = 1735325299900396750
The text was updated successfully, but these errors were encountered:
No branches or pull requests
When querying data in the v1 shell the timestanps are wrong:
environment
steps to reproduce
influx v1 shell
use "my_db"
precision ns
SELECT time,temp FROM "heating" WHERE temp=0
expected result
the returned timestamps should be correct and in nanosecond precision
actual result
the returned timestamps are incorrect
example:
proof that timestamps are incorrect
the corresponding entry is:
heating,,1735325299900396750,0
DELETE FROM "heating" WHERE time = 1735325299900396800
--> entry is not deletedDELETE FROM "heating" WHERE time = 1735325299900396750
--> entry is deletedThe text was updated successfully, but these errors were encountered: