What needs to happen?

The module runners/core-construction-java is no longer needed and makes it annoying and boilerplate to make portable transforms using the service loader interface pattern, which is not appropriate anymore.

The origin of the module was specifically so the Java SDK would not depend on protobuf or portability. The philosophy back then was that each SDK should stand on its own, and portability would be a handy plugin if you wanted it. Mostly, a runner would choose to be a portability-based runner.

Now that is obsolete. Every SDK depends on portability, or will soon, and every runner as well. It is the heart of the Beam model. We have also gone far enough that we are totally committed to protobuf and gRPC.

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