[Tracking]: Beam 3.0.0 Milestone 1 Java SDK breaking changes #35836
Description
What needs to happen?
This umbrella tracks any changes could affect existing users (breaking changes) made to Beam Java 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
| Task | sub task (if exists) | version (proposed) | Notes |
|---|---|---|---|
| Java modernization | |||
| Java 8 is officially deprecated. Java 8 pipeline runs on Java11 container (#35064) | 2.66.0 | ||
| Beam infra requires Java11+ (#35586) | 2.67.0dev | ||
| End Java 8 support (#31678) | (3.0.0) | ||
| Java 25 support (#35627) | 2.69 | ||
| Beam SQL modernization | |||
| Beam ZetaSQL is officially deprecated (#34563) | 2.65.0 | ||
| End Beam ZetaSQL support (#35662) | 2.68.0 | ||
| Upgrade Calcite to 1.40 (#35718) | 2.68.0 | ||
| Runner modernization | |||
| End Samza runner support (#35448) | (3.0.0) | ||
| End Twister2 runner (non-portable) support (#35905) | (3.0.0 or later) | ||
| Deprecate (non-portable) Jet runner (#35907) | (3.0.0 or later) | ||
| Flag/default behavior changes | |||
| BigQueryIO streaming default write method from STREAMING_INSERT to STORAGE_API_AT_LEAST_ONCE (or STORAGE_WRITE_API) (#31827) | |||
| Coder deduplications (#34637) |
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