feat: nanosecond timestamp support #118
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
kafka1991
force-pushed
the
timestamp_nanos
branch
from
6332d38 to
7ebe0c0
Compare
amunra
reviewed
Sep 11, 2025
amunra
approved these changes
Sep 12, 2025
amunra
changed the title
column_ts pass timestamp value in nanoseconds instead of microseconds
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 PR adds nanosecond support.
The client already exposed APIs that accepted both microseconds and nanosecond.
Before this change, the nanosecond APIs would convert to microseconds for the non-designated timestamp column. Now the nanosecond APIs pass the data through as-is.
This change is being introduced in conjunction with questdb/questdb#5685 which adds native nanosecond precision timestamps to the database.