[
https://issues.apache.org/jira/browse/BEAM-5464?focusedWorklogId=161245&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-161245
]
ASF GitHub Bot logged work on BEAM-5464:
----------------------------------------
Author: ASF GitHub Bot
Created on: 31/Oct/18 17:41
Start Date: 31/Oct/18 17:41
Worklog Time Spent: 10m
Work Description: angoenka commented on a change in pull request #6897:
[BEAM-5464] Use BATCH_FORCED as the default ExecutionMode for batch pipeline
URL: https://github.com/apache/beam/pull/6897#discussion_r229799016
##########
File path:
runners/flink/src/main/java/org/apache/beam/runners/flink/FlinkPipelineOptions.java
##########
@@ -187,4 +188,12 @@
Long getLatencyTrackingInterval();
void setLatencyTrackingInterval(Long interval);
+
+ @Description(
+ "Flink mode for data exchange for batch pipeline. "
+ + "Reference {@link org.apache.flink.api.common.ExecutionMode}")
+ @Default.Enum("BATCH_FORCED")
+ ExecutionMode getExecutionModeForBatch();
Review comment:
TheDefault Enum test is done in ProxyInvocationHandlerTest.java
Please let me know if you are referring to some other test.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 161245)
Time Spent: 1h 20m (was: 1h 10m)
> Portable beam hangs while running TFX preprocessing step on a distributed
> cluster
> ---------------------------------------------------------------------------------
>
> Key: BEAM-5464
> URL: https://issues.apache.org/jira/browse/BEAM-5464
> Project: Beam
> Issue Type: Bug
> Components: java-fn-execution
> Reporter: Axel Magnuson
> Assignee: Ankur Goenka
> Priority: Major
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Recently I went through the exercise of running the TFX taxi example on a
> dataproc cluster. However it would always hang indefinitely. The flink UI
> indicated that the job was halfway done. However I could not see any clear
> errors in the job driver logs, the job service logs, or the Flink logs. The
> root cause is still a mystery to me.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
