influx v1 shell returns wrong timestamps

[tom-ch1]

When querying data in the v1 shell the timestanps are wrong:

environment

• OS: Debian: GNU/Linux 12 (bookworm)
• influx version: Influx CLI dev (git: a79a2a1b825867421d320428538f76a4c90aa34c) build_date: 2024-04-16T14:34:32Z
• retention periods for the bucket in question:

SHOW RETENTION POLICIES ON my_db
name,tags,name,duration,shardGroupDuration,replicaN,default
,,autogen,0s,168h0m0s,replicaN,true

steps to reproduce

1. influx v1 shell
2. use "my_db"
3. precision ns
4. 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:

• timestamp for first entry is: "1735325299900396800.0000000000"
• however, it should be: "1735325299900396750"

proof that timestamps are incorrect

• if I query the database using the REST API, I get the correct timestamp:

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

• if I now try to delete the entry using influx v1 shell according to the timestamp, the entry gets deleted only if I indicate the correct timestamp:
  • DELETE FROM "heating" WHERE time = 1735325299900396800 --> entry is not deleted
  • DELETE FROM "heating" WHERE time = 1735325299900396750 --> entry is deleted