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_r405892635
##########
File path:
runners/google-cloud-dataflow-java/worker/src/main/java/org/apache/beam/runners/dataflow/worker/graph/RegisterNodeFunction.java
##########
@@ -134,14 +136,18 @@ public static RegisterNodeFunction forPipeline(
* harnesses, then this method should be removed.
*/
public static RegisterNodeFunction withoutPipeline(
- IdGenerator idGenerator, Endpoints.ApiServiceDescriptor
stateApiServiceDescriptor) {
- return new RegisterNodeFunction(null, idGenerator,
stateApiServiceDescriptor);
+ IdGenerator idGenerator,
+ Endpoints.ApiServiceDescriptor stateApiServiceDescriptor,
+ Endpoints.ApiServiceDescriptor timerApiServiceDescriptor) {
+ return new RegisterNodeFunction(
+ null, idGenerator, stateApiServiceDescriptor,
timerApiServiceDescriptor);
}
private RegisterNodeFunction(
@Nullable RunnerApi.Pipeline pipeline,
IdGenerator idGenerator,
- Endpoints.ApiServiceDescriptor stateApiServiceDescriptor) {
+ Endpoints.ApiServiceDescriptor stateApiServiceDescriptor,
+ Endpoints.ApiServiceDescriptor timerApiServiceDescriptor) {
Review comment:
timerApiServiceDescriptor isn't used? Should it be stored and written to the
ProcessBundleDescrioptor?
----------------------------------------------------------------
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
