Skip to content

[Feature Request]: Upgrade to Iceberg >1.7.0 and support timestamp nano types #34098

Closed as not planned

Description

@ahmedabu98

What would you like to happen?

Iceberg spec V3 introduces new timestamp types timestamp_ns and timestamptz_ns for nanosecond precision (apache/iceberg#9008).

We should upgrade to a later version that includes these types and add support for conversion in our IcebergUtils.

Issue Priority

Priority: 2 (default / most feature requests should be filed as P2)

Issue Components

  • Component: Python SDK
  • Component: Java SDK
  • Component: Go SDK
  • Component: Typescript SDK
  • Component: IO connector
  • Component: Beam YAML
  • Component: Beam examples
  • Component: Beam playground
  • Component: Beam katas
  • Component: Website
  • Component: Infrastructure
  • Component: Spark Runner
  • Component: Flink Runner
  • Component: Samza Runner
  • Component: Twister2 Runner
  • Component: Hazelcast Jet Runner
  • Component: Google Cloud Dataflow Runner

Activity

  1. added
    IcebergIOIcebergIO: can only be used through ManagedIO
    on Mar 4, 2025
  2. github-actions commented on Aug 2, 2025

    @github-actions
    Contributor

    This issue has been marked as stale due to 150 days of inactivity. It will be closed in 30 days if no further activity occurs. If you think that’s incorrect or this issue still needs to be addressed, please simply write any comment. If closed, you can reopen the issue at any time. Thank you for your contributions.

  3. masfworld commented on Aug 26, 2025

    @masfworld

    I think it's very important to upgrade Iceberg. There are a bunch of bugs and new features missed.
    For me, this is critical apache/iceberg#11282

  4. ahmedabu98 commented on Aug 27, 2025

    @ahmedabu98
    ContributorAuthor

    We were waiting to update directly to Iceberg version 1.10.0

    But considering the bugs you mention and how it's still taking them some time to get a release going, I think we should upgrade to 1.9.2 for now

  5. github-actions commented on Jan 25, 2026

    @github-actions
    Contributor

    This issue has been marked as stale due to 150 days of inactivity. It will be closed in 30 days if no further activity occurs. If you think that’s incorrect or this issue still needs to be addressed, please simply write any comment. If closed, you can reopen the issue at any time. Thank you for your contributions.

  6. github-actions commented on Jul 19, 2026

    @github-actions
    Contributor

    This issue has been marked as stale due to 150 days of inactivity. It will be closed in 30 days if no further activity occurs. If you think that’s incorrect or this issue still needs to be addressed, please simply write any comment. If closed, you can reopen the issue at any time. Thank you for your contributions.

  7. github-actions commented on Aug 19, 2026

    @github-actions
    Contributor

    This issue has been closed due to lack of activity. If you think that is incorrect, you can reopen the issue at any time.

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

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions