Running the Apache Beam samples With the Beam Direct Runner

Using the Direct Runner for testing and development helps ensure that pipelines are robust across different Beam runners. In addition, debugging failed runs can be a non-trivial task when a pipeline executes on a remote cluster. Instead, it is often faster and simpler to perform local unit testing on your pipeline code. Unit testing your pipeline locally also allows you to use your preferred local debugging tools.

The default settings for the direct runner should work by default, all you need to do is specify your fat jar location.

Contrary to the Flink and runners, the direct runner can be started directly from Hop Gui.