Skip to content

feat: Nanosecond timestamps [WIP proof-of-concept for protocol RFC]#4215

Draft
itamarst wants to merge 3 commits intodelta-io:mainfrom
itamarst:nanosecond-timestamps
Draft

feat: Nanosecond timestamps [WIP proof-of-concept for protocol RFC]#4215
itamarst wants to merge 3 commits intodelta-io:mainfrom
itamarst:nanosecond-timestamps

Conversation

@itamarst
Copy link

@itamarst itamarst commented Feb 19, 2026

This is a proof-of-concept of adding nanosecond timestamps, part of a protocol RFC: delta-io/delta#6081

There is a corresponding PR against delta-kernel-rs: delta-io/delta-kernel-rs#1897

Future work that would need to be done:

  • Deciding whether nanosecond timestamps should be supported by default.
  • Previously nanosecond timestamp columns were automatically converted to microsecond. This changes the behavior to preserving them as nanosecond. I can imagine a desirable behavior being keeping the old auto-conversion if the nanoseconds timestamps table feature is disabled. The current tests were updated with assumption that nanosecond stays as nanosecond, but that may be annoying for users who use multiple libraries and who suddenly and unexpectedly have tables with unsupported nanosecond timestamps.

@github-actions github-actions bot added binding/python Issues for the Python package binding/rust Issues for the Rust crate labels Feb 19, 2026
@github-actions
Copy link

ACTION NEEDED

delta-rs follows the Conventional Commits specification for release automation.

The PR title and description are used as the merge commit message. Please update your PR title and description to match the specification.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

binding/python Issues for the Python package binding/rust Issues for the Rust crate

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

2 participants