Yeah, take a look at the ProcessRemoteBundleOperation.java <https://github.com/apache/beam/blob/master/runners/google-cloud-dataflow-java/worker/src/main/java/org/apache/beam/runners/dataflow/worker/fn/control/ProcessRemoteBundleOperation.java> class. This is the class that is in charge of handling bundle execution. You can create a new implementation of the BundleProgressHandler.java <https://github.com/apache/beam/blob/master/runners/java-fn-execution/src/main/java/org/apache/beam/runners/fnexecution/control/BundleProgressHandler.java>, and give that to the ProcessRemoteBundleOperation in the BeamFnMapTaskExecutorFactory.java <https://github.com/apache/beam/blob/b83b302ef97767e4ca245ea24e8bd40a6692e72c/runners/google-cloud-dataflow-java/worker/src/main/java/org/apache/beam/runners/dataflow/worker/BeamFnMapTaskExecutorFactory.java#L349>. Currently the progress handler is "ignored", so you will be the first implementation using ExecutableStages.
On Tue, Feb 5, 2019 at 11:09 AM Alex Amato <ajam...@google.com> wrote: > I filed a JIRA to introduce ProcesSBundleProgressResponses, which are not > yet implemented in the java SDK. I just wanted to make sure what I put down > here is the correct approach? > > I wrote down a few places in the code where I thought it might be needed in > https://jira.apache.org/jira/browse/BEAM-6597 > > I recall Luke once suggesting that this could be done by overrding some > progress method that already existed. In ProcessBundleHandler or some layer > which invokes it? But I could be making this up. > > I was wondering if anyone else had a good sense for this. >
