Skip to content

[Feature Request]: Define an expansion service jar for Delta Lake #38561

Closed

Description

@chamikaramj

What would you like to happen?

For context, please see s.apache.org/beam-delta-lake-source.

Given that potential size of the transitive dependencies of the Delta Lake connector and due to needing Java 17, I suggest defining a new expansion service jar for this.

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: Prism Runner
  • Component: Twister2 Runner
  • Component: Hazelcast Jet Runner
  • Component: Google Cloud Dataflow Runner

Activity

  1. chamikaramj commented on May 27, 2026

    @chamikaramj
    ContributorAuthor

    We need to either a new expansion service jar to support Managed Delta Lake source.

  2. derrickaw commented on Jun 13, 2026

    @derrickaw
    Collaborator

    upgraded expansion service to use Java 17 to work with Delta Lake - #38931

  3. derrickaw commented on Jul 1, 2026

    @derrickaw
    Collaborator

    I think this is done unless @chamikaramj you see a reason why we need to do this? Thanks

  4. chamikaramj commented on Aug 15, 2026

    @chamikaramj
    ContributorAuthor

    We added Delta Lake IO to I/O expansion service instead: #39052

    Closing this.

  5. added this to the 2.77.0 Release milestone on Aug 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions