-
Notifications
You must be signed in to change notification settings - Fork 478
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
Add possibility to let InfluxDB handle the timestamp itself #349
Comments
#312 is addressing this issue, i liked the approach, but the current author is not able to fix merge conflicts. So if you are interested you can catch up there. |
The line protocol states that "Timestamp" is optional. Am I missing something? |
Working on a fix. |
Due to a bad support of accurate timestamps (especially in older Java versions) I would love to let InfluxDB handle the timestamps by itself.
read more
As I have several data-points in a single measurement per second and it is not very recommended to have a unique-id in a tag (performance reasons) I would like to have an accurate timestamp. Otherwise I would loose data!
In the method build of Point I found the following behavior:
So, if no time is provided for a certain point this library does not what I want it to do. I can't find any simple way to let InfluxDB handle the timestamp using this library?
The text was updated successfully, but these errors were encountered: