feat(nodejs): nanos precision for timestamps #55
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
amunra
reviewed
Oct 13, 2025
amunra
reviewed
Oct 13, 2025
amunra
reviewed
Oct 13, 2025
amunra
approved these changes
Oct 13, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change brings nanosecond precision support for timestamps in the client.
It complements a recent change on the server side, - the introduction of the
TIMESTAMP_NStype.This new column type can store timestamps with nanoseconds precision.
Now when using protocol v2, any timestamp passed to the client in nanoseconds (unit 'ns') will be sent to the server with nanos precision.
Everything else is sent with micros precision, just as before.
The above is the same for timestamp columns and for the designated timestamp too.
Protocol v1 is not changing, it is kept backwards and InfluxDB compatible.
All timestamp column values are sent with micros precision, and it uses nanos precision for the designated timestamp.
Please, note that although designated timestamp values have always been sent with nanos precision, the server stored them as micros as it had no support for nanos precision.