[ 
https://issues.apache.org/jira/browse/BEAM-5239?focusedWorklogId=139632&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-139632
 ]

ASF GitHub Bot logged work on BEAM-5239:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 30/Aug/18 10:16
            Start Date: 30/Aug/18 10:16
    Worklog Time Spent: 10m 
      Work Description: aljoscha commented on a change in pull request #6278: 
[BEAM-5239] Enable to configure latencyTrackingInterval
URL: https://github.com/apache/beam/pull/6278#discussion_r213977137
 
 

 ##########
 File path: 
runners/flink/src/main/java/org/apache/beam/runners/flink/FlinkExecutionEnvironments.java
 ##########
 @@ -171,4 +176,12 @@ public static StreamExecutionEnvironment 
createStreamExecutionEnvironment(
 
     return flinkStreamEnv;
   }
+
+  private static void applyLatencyTrackingInterval(
+      ExecutionConfig config, FlinkPipelineOptions options) {
+    long latencyTrackingInterval = options.getLatencyTrackingInterval();
+    if (latencyTrackingInterval >= 0) {
 
 Review comment:
   Will this work? The default is `-1`, so this condition will be `false`, i.e. 
we never disable latency tracking in Flink which is the original point of this 
PR.
   
   I think we can just remove the check. What do you think?

----------------------------------------------------------------
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: 139632)
    Time Spent: 1h 20m  (was: 1h 10m)

> Allow configure latencyTrackingInterval
> ---------------------------------------
>
>                 Key: BEAM-5239
>                 URL: https://issues.apache.org/jira/browse/BEAM-5239
>             Project: Beam
>          Issue Type: New Feature
>          Components: runner-flink
>    Affects Versions: 2.6.0
>            Reporter: Jozef Vilcek
>            Assignee: Aljoscha Krettek
>            Priority: Major
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Because of FLINK-10226, we need to be able to set 
> latencyTrackingConfiguration for flink via FlinkPipelineOptions



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to