Skip to content

[Task]: Reconsider the need to stage Beam SDK to GCS after removing runner v1 support. #26996

@tvalentyn

Description

@tvalentyn

What needs to happen?

SDK now uses Beam-provided containers as execution environment on Dataflow. It may no longer be necessary to stage the SDK to staging location, or at minimum, it should not be a requirement on runner v2 pipelines.

Issue Priority

Priority: 3 (nice-to-have improvement)

Issue Components

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

Metadata

Metadata

Assignees

Labels

P3dataflowdone & doneIssue has been reviewed after it was closed for verification, followups, etc.pythontask

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions