Skip to content

[Tracking]: Beam 3.0.0 Milestone 1 Python SDK breaking changes #36101

@Abacn

Description

@Abacn

What needs to happen?

This umbrella issue tracks any changes could affect existing users (breaking changes) made to Beam Python SDK as part of Beam 3 effort. Changes not necessarily happen for 2.x -> 3.0 at once. Instead incrementally, and actual breaking change happens at Beam 3.0.0 (Milestone 3).

Task sub task (if exists) version (proposed) Notes
Changed the default Python runner to be prism (#34549) 2.68.0
Changed the default pickle library to cloudpickle (#21298) 2.65.0
The deterministic fallback coder changed to use cloudpickle (#35725) 2.68.0
Made dill dependency optional (#36093) 2.69.0

Issue Priority

Priority: 2 (default / most normal work 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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions