TheNeuralBit commented on a change in pull request #11314: [BEAM-9562] Send
Timers over Data Channel as Elements
URL: https://github.com/apache/beam/pull/11314#discussion_r405890215
##########
File path:
runners/google-cloud-dataflow-java/worker/src/main/java/org/apache/beam/runners/dataflow/worker/BatchDataflowWorker.java
##########
@@ -238,9 +238,14 @@ protected BatchDataflowWorker(
sdkFusedStage =
pipeline == null
? RegisterNodeFunction.withoutPipeline(
- idGenerator,
sdkHarnessRegistry.beamFnStateApiServiceDescriptor())
+ idGenerator,
+ sdkHarnessRegistry.beamFnStateApiServiceDescriptor(),
+ sdkHarnessRegistry.beamFnDataApiServiceDescriptor())
Review comment:
I see. So we only have a separate timer_api_service_descriptor in the protos
so that a runner has the option to make it separate, but it doesn't need to be
separate?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
With regards,
Apache Git Services
