-
Notifications
You must be signed in to change notification settings - Fork 133
Writing data with less than second precision #145
New issue
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
Comments
Here is the spec that I was following https://github.com/influxdata/influxdb-ruby/blob/master/spec/influxdb/cases/write_points_spec.rb#L104 |
This might be a bug in the test, I will have a closer look tomorrow. Which version of InfluxDB were you testing against? |
0.13
|
I believe the test is indeed faulty: |
Yeah I tried it with ms too and same error.
|
The weird thing that happens is if I dont send any timestamp value and let Influx handle that I end up with second precision. |
So I figured out the issue I think. Basically I am trying to write a bunch of data to 1 database. Some of that data is coming from telegraf and I think its resolution (even though I have it configured differently) is to the second. If I create a new database and write the data with the ruby client with millisecond precision everything seems to work just fine. |
closing this issue as i figured out my problem. |
So I am trying to write data with either millisecond or nanosecond precision and neither works.
If I try to generate an integer that represents millisecond precision (since epoch):
I get the following error:
I am trying to do what the tests show but that doesn't seem to be working
The text was updated successfully, but these errors were encountered: