[jira] [Work logged] (BEAM-5239) Allow configure latencyTrackingInterval
[ https://issues.apache.org/jira/browse/BEAM-5239?focusedWorklogId=144877=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-144877 ] ASF GitHub Bot logged work on BEAM-5239: Author: ASF GitHub Bot Created on: 17/Sep/18 15:27 Start Date: 17/Sep/18 15:27 Worklog Time Spent: 10m Work Description: JozoVilcek commented on a change in pull request #6278: [BEAM-5239] Enable to configure latencyTrackingInterval URL: https://github.com/apache/beam/pull/6278#discussion_r218115490 ## File path: runners/flink/src/main/java/org/apache/beam/runners/flink/FlinkPipelineOptions.java ## @@ -167,4 +167,12 @@ Boolean isShutdownSourcesOnFinalWatermark(); void setShutdownSourcesOnFinalWatermark(Boolean shutdownOnFinalWatermark); + + @Description( + "Interval in milliseconds for sending latency tracking marks from the sources to the sinks. " Review comment: Sorry, I was offline to a while. Thanks a lot for getting this through! 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: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 144877) Time Spent: 3.5h (was: 3h 20m) > 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: Jozef Vilcek >Priority: Major > Fix For: 2.8.0 > > Time Spent: 3.5h > 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)
[jira] [Work logged] (BEAM-5239) Allow configure latencyTrackingInterval
[ https://issues.apache.org/jira/browse/BEAM-5239?focusedWorklogId=144878=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-144878 ] ASF GitHub Bot logged work on BEAM-5239: Author: ASF GitHub Bot Created on: 17/Sep/18 15:27 Start Date: 17/Sep/18 15:27 Worklog Time Spent: 10m Work Description: JozoVilcek commented on a change in pull request #6278: [BEAM-5239] Enable to configure latencyTrackingInterval URL: https://github.com/apache/beam/pull/6278#discussion_r218115490 ## File path: runners/flink/src/main/java/org/apache/beam/runners/flink/FlinkPipelineOptions.java ## @@ -167,4 +167,12 @@ Boolean isShutdownSourcesOnFinalWatermark(); void setShutdownSourcesOnFinalWatermark(Boolean shutdownOnFinalWatermark); + + @Description( + "Interval in milliseconds for sending latency tracking marks from the sources to the sinks. " Review comment: Sorry, I was offline for a while. Thanks a lot for getting this through! 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: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 144878) Time Spent: 3h 40m (was: 3.5h) > 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: Jozef Vilcek >Priority: Major > Fix For: 2.8.0 > > Time Spent: 3h 40m > 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)
[jira] [Work logged] (BEAM-5239) Allow configure latencyTrackingInterval
[ https://issues.apache.org/jira/browse/BEAM-5239?focusedWorklogId=143168=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-143168 ] ASF GitHub Bot logged work on BEAM-5239: Author: ASF GitHub Bot Created on: 11/Sep/18 16:02 Start Date: 11/Sep/18 16:02 Worklog Time Spent: 10m Work Description: mxm commented on a change in pull request #6278: [BEAM-5239] Enable to configure latencyTrackingInterval URL: https://github.com/apache/beam/pull/6278#discussion_r216725538 ## File path: runners/flink/src/main/java/org/apache/beam/runners/flink/FlinkPipelineOptions.java ## @@ -167,4 +167,12 @@ Boolean isShutdownSourcesOnFinalWatermark(); void setShutdownSourcesOnFinalWatermark(Boolean shutdownOnFinalWatermark); + + @Description( + "Interval in milliseconds for sending latency tracking marks from the sources to the sinks. " Review comment: Merged this with a whitespace fix applied in the merge commit. 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: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 143168) Time Spent: 3h 20m (was: 3h 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: Jozef Vilcek >Priority: Major > Fix For: 2.7.0 > > Time Spent: 3h 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)
[jira] [Work logged] (BEAM-5239) Allow configure latencyTrackingInterval
[
https://issues.apache.org/jira/browse/BEAM-5239?focusedWorklogId=143167=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-143167
]
ASF GitHub Bot logged work on BEAM-5239:
Author: ASF GitHub Bot
Created on: 11/Sep/18 16:02
Start Date: 11/Sep/18 16:02
Worklog Time Spent: 10m
Work Description: asfgit closed pull request #6278: [BEAM-5239] Enable to
configure latencyTrackingInterval
URL: https://github.com/apache/beam/pull/6278
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git
a/runners/flink/src/main/java/org/apache/beam/runners/flink/FlinkExecutionEnvironments.java
b/runners/flink/src/main/java/org/apache/beam/runners/flink/FlinkExecutionEnvironments.java
index 1162a7ed95a..bf06d0b6699 100644
---
a/runners/flink/src/main/java/org/apache/beam/runners/flink/FlinkExecutionEnvironments.java
+++
b/runners/flink/src/main/java/org/apache/beam/runners/flink/FlinkExecutionEnvironments.java
@@ -19,6 +19,7 @@
import com.google.common.base.Splitter;
import java.util.List;
+import org.apache.flink.api.common.ExecutionConfig;
import org.apache.flink.api.java.CollectionEnvironment;
import org.apache.flink.api.java.ExecutionEnvironment;
import org.apache.flink.runtime.state.AbstractStateBackend;
@@ -78,6 +79,8 @@ public static ExecutionEnvironment
createBatchExecutionEnvironment(
flinkBatchEnv.getConfig().disableObjectReuse();
}
+applyLatencyTrackingInterval(flinkBatchEnv.getConfig(), options);
+
return flinkBatchEnv;
}
@@ -163,6 +166,8 @@ public static StreamExecutionEnvironment
createStreamExecutionEnvironment(
}
}
+applyLatencyTrackingInterval(flinkStreamEnv.getConfig(), options);
+
// State backend
final AbstractStateBackend stateBackend = options.getStateBackend();
if (stateBackend != null) {
@@ -171,4 +176,10 @@ public static StreamExecutionEnvironment
createStreamExecutionEnvironment(
return flinkStreamEnv;
}
+
+ private static void applyLatencyTrackingInterval(
+ ExecutionConfig config, FlinkPipelineOptions options) {
+long latencyTrackingInterval = options.getLatencyTrackingInterval();
+config.setLatencyTrackingInterval(latencyTrackingInterval);
+ }
}
diff --git
a/runners/flink/src/main/java/org/apache/beam/runners/flink/FlinkPipelineOptions.java
b/runners/flink/src/main/java/org/apache/beam/runners/flink/FlinkPipelineOptions.java
index 52b44401ed2..437d09c4295 100644
---
a/runners/flink/src/main/java/org/apache/beam/runners/flink/FlinkPipelineOptions.java
+++
b/runners/flink/src/main/java/org/apache/beam/runners/flink/FlinkPipelineOptions.java
@@ -167,4 +167,12 @@
Boolean isShutdownSourcesOnFinalWatermark();
void setShutdownSourcesOnFinalWatermark(Boolean shutdownOnFinalWatermark);
+
+ @Description(
+ "Interval in milliseconds for sending latency tracking marks from the
sources to the sinks. "
+ + "Interval value <= 0 disables the feature.")
+ @Default.Long(0)
+ Long getLatencyTrackingInterval();
+
+ void setLatencyTrackingInterval(Long interval);
}
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:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 143167)
Time Spent: 3h 10m (was: 3h)
> 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: Jozef Vilcek
>Priority: Major
> Fix For: 2.7.0
>
> Time Spent: 3h 10m
> 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)
[jira] [Work logged] (BEAM-5239) Allow configure latencyTrackingInterval
[ https://issues.apache.org/jira/browse/BEAM-5239?focusedWorklogId=140928=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-140928 ] ASF GitHub Bot logged work on BEAM-5239: Author: ASF GitHub Bot Created on: 04/Sep/18 14:49 Start Date: 04/Sep/18 14:49 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_r214945569 ## File path: runners/flink/src/main/java/org/apache/beam/runners/flink/FlinkPipelineOptions.java ## @@ -167,4 +167,12 @@ Boolean isShutdownSourcesOnFinalWatermark(); void setShutdownSourcesOnFinalWatermark(Boolean shutdownOnFinalWatermark); + + @Description( + "Interval in milliseconds for sending latency tracking marks from the sources to the sinks. " Review comment: See here: https://builds.apache.org/job/beam_PreCommit_Java_Commit/1182/consoleFull at the end. 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: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 140928) Time Spent: 3h (was: 2h 50m) > 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: 3h > 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)
[jira] [Work logged] (BEAM-5239) Allow configure latencyTrackingInterval
[ https://issues.apache.org/jira/browse/BEAM-5239?focusedWorklogId=140927=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-140927 ] ASF GitHub Bot logged work on BEAM-5239: Author: ASF GitHub Bot Created on: 04/Sep/18 14:49 Start Date: 04/Sep/18 14:49 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_r214945463 ## File path: runners/flink/src/main/java/org/apache/beam/runners/flink/FlinkPipelineOptions.java ## @@ -167,4 +167,12 @@ Boolean isShutdownSourcesOnFinalWatermark(); void setShutdownSourcesOnFinalWatermark(Boolean shutdownOnFinalWatermark); + + @Description( + "Interval in milliseconds for sending latency tracking marks from the sources to the sinks. " Review comment: The build is failing because spotless is complaining about the space after this line. 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: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 140927) Time Spent: 2h 50m (was: 2h 40m) > 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: 2h 50m > 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)
[jira] [Work logged] (BEAM-5239) Allow configure latencyTrackingInterval
[ https://issues.apache.org/jira/browse/BEAM-5239?focusedWorklogId=140620=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-140620 ] ASF GitHub Bot logged work on BEAM-5239: Author: ASF GitHub Bot Created on: 03/Sep/18 15:43 Start Date: 03/Sep/18 15:43 Worklog Time Spent: 10m Work Description: aljoscha commented on issue #6278: [BEAM-5239] Enable to configure latencyTrackingInterval URL: https://github.com/apache/beam/pull/6278#issuecomment-418148765 Run Flink ValidatesRunner 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: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 140620) Time Spent: 2.5h (was: 2h 20m) > 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: 2.5h > 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)
[jira] [Work logged] (BEAM-5239) Allow configure latencyTrackingInterval
[ https://issues.apache.org/jira/browse/BEAM-5239?focusedWorklogId=140621=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-140621 ] ASF GitHub Bot logged work on BEAM-5239: Author: ASF GitHub Bot Created on: 03/Sep/18 15:43 Start Date: 03/Sep/18 15:43 Worklog Time Spent: 10m Work Description: aljoscha commented on issue #6278: [BEAM-5239] Enable to configure latencyTrackingInterval URL: https://github.com/apache/beam/pull/6278#issuecomment-418148799 retest this please 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: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 140621) Time Spent: 2h 40m (was: 2.5h) > 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: 2h 40m > 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)
[jira] [Work logged] (BEAM-5239) Allow configure latencyTrackingInterval
[
https://issues.apache.org/jira/browse/BEAM-5239?focusedWorklogId=139675=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-139675
]
ASF GitHub Bot logged work on BEAM-5239:
Author: ASF GitHub Bot
Created on: 30/Aug/18 13:09
Start Date: 30/Aug/18 13:09
Worklog Time Spent: 10m
Work Description: mxm commented on a change in pull request #6278:
[BEAM-5239] Enable to configure latencyTrackingInterval
URL: https://github.com/apache/beam/pull/6278#discussion_r214023347
##
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:
The default is now 0, so it gets disabled by default now. I agree with
Aljoscha that the check could be removed entirely. The problem is, if you pass
in negative numbers, they will simply be ignored and latency tracking will
still be enabled...
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:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 139675)
Time Spent: 2h 20m (was: 2h 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: 2h 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)
[jira] [Work logged] (BEAM-5239) Allow configure latencyTrackingInterval
[ https://issues.apache.org/jira/browse/BEAM-5239?focusedWorklogId=139674=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-139674 ] ASF GitHub Bot logged work on BEAM-5239: Author: ASF GitHub Bot Created on: 30/Aug/18 13:09 Start Date: 30/Aug/18 13:09 Worklog Time Spent: 10m Work Description: mxm commented on a change in pull request #6278: [BEAM-5239] Enable to configure latencyTrackingInterval URL: https://github.com/apache/beam/pull/6278#discussion_r214021455 ## File path: runners/flink/src/main/java/org/apache/beam/runners/flink/FlinkPipelineOptions.java ## @@ -167,4 +167,12 @@ Boolean isShutdownSourcesOnFinalWatermark(); void setShutdownSourcesOnFinalWatermark(Boolean shutdownOnFinalWatermark); + + @Description( + "Interval in milliseconds for sending latency tracking marks from the sources to the sinks. " + + "Interval value = 0 disablesthe feature.") Review comment: space missing `disablesthe` 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: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 139674) Time Spent: 2h 10m (was: 2h) > 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: 2h 10m > 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)
[jira] [Work logged] (BEAM-5239) Allow configure latencyTrackingInterval
[ https://issues.apache.org/jira/browse/BEAM-5239?focusedWorklogId=139647=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-139647 ] ASF GitHub Bot logged work on BEAM-5239: Author: ASF GitHub Bot Created on: 30/Aug/18 11:42 Start Date: 30/Aug/18 11:42 Worklog Time Spent: 10m Work Description: aljoscha commented on issue #6278: [BEAM-5239] Enable to configure latencyTrackingInterval URL: https://github.com/apache/beam/pull/6278#issuecomment-417289738 Ah, Jenkins is down: https://status.apache.org 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: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 139647) Time Spent: 2h (was: 1h 50m) > 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: 2h > 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)
[jira] [Work logged] (BEAM-5239) Allow configure latencyTrackingInterval
[
https://issues.apache.org/jira/browse/BEAM-5239?focusedWorklogId=139646=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-139646
]
ASF GitHub Bot logged work on BEAM-5239:
Author: ASF GitHub Bot
Created on: 30/Aug/18 11:40
Start Date: 30/Aug/18 11:40
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_r213997293
##
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:
I think we should disable by default. This is also what will happen for the
next Flink version, I think. And it might save people some headaches if they
don't have to debug it and find out the hard way, as you did.
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:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 139646)
Time Spent: 1h 50m (was: 1h 40m)
> 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 50m
> 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)
[jira] [Work logged] (BEAM-5239) Allow configure latencyTrackingInterval
[
https://issues.apache.org/jira/browse/BEAM-5239?focusedWorklogId=139639=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-139639
]
ASF GitHub Bot logged work on BEAM-5239:
Author: ASF GitHub Bot
Created on: 30/Aug/18 10:41
Start Date: 30/Aug/18 10:41
Worklog Time Spent: 10m
Work Description: JozoVilcek commented on a change in pull request #6278:
[BEAM-5239] Enable to configure latencyTrackingInterval
URL: https://github.com/apache/beam/pull/6278#discussion_r213983463
##
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:
Idea was to stick to default flink configuration, unless user intend to
overwrite it. With this PR I have a choice to disable it by passing to runner
`--latencyTrackingInterval=0`.
Did not wanted to disable it for all by default. Should I?
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:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 139639)
Time Spent: 1h 40m (was: 1.5h)
> 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 40m
> 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)
[jira] [Work logged] (BEAM-5239) Allow configure latencyTrackingInterval
[ https://issues.apache.org/jira/browse/BEAM-5239?focusedWorklogId=139633=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-139633 ] ASF GitHub Bot logged work on BEAM-5239: Author: ASF GitHub Bot Created on: 30/Aug/18 10:18 Start Date: 30/Aug/18 10:18 Worklog Time Spent: 10m Work Description: aljoscha commented on issue #6278: [BEAM-5239] Enable to configure latencyTrackingInterval URL: https://github.com/apache/beam/pull/6278#issuecomment-417268836 Run Flink ValidatesRunner 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: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 139633) Time Spent: 1.5h (was: 1h 20m) > 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: 1.5h > 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)
[jira] [Work logged] (BEAM-5239) Allow configure latencyTrackingInterval
[
https://issues.apache.org/jira/browse/BEAM-5239?focusedWorklogId=139632=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:
us...@infra.apache.org
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)
[jira] [Work logged] (BEAM-5239) Allow configure latencyTrackingInterval
[ https://issues.apache.org/jira/browse/BEAM-5239?focusedWorklogId=139145=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-139145 ] ASF GitHub Bot logged work on BEAM-5239: Author: ASF GitHub Bot Created on: 29/Aug/18 07:30 Start Date: 29/Aug/18 07:30 Worklog Time Spent: 10m Work Description: angoenka commented on a change in pull request #6278: [BEAM-5239] Enable to configure latencyTrackingInterval URL: https://github.com/apache/beam/pull/6278#discussion_r213571798 ## File path: runners/flink/src/main/java/org/apache/beam/runners/flink/FlinkPipelineOptions.java ## @@ -167,4 +167,11 @@ Boolean isShutdownSourcesOnFinalWatermark(); void setShutdownSourcesOnFinalWatermark(Boolean shutdownOnFinalWatermark); + + @Description( + "Interval in milliseconds for sending latency tracking marks from the sources to the sinks.") + @Default.Long(-1L) + Long getLatencyTrackingInterval(); Review comment: I see, Sounds reasonable. 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: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 139145) Time Spent: 1h 10m (was: 1h) > 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 10m > 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)
[jira] [Work logged] (BEAM-5239) Allow configure latencyTrackingInterval
[
https://issues.apache.org/jira/browse/BEAM-5239?focusedWorklogId=139144=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-139144
]
ASF GitHub Bot logged work on BEAM-5239:
Author: ASF GitHub Bot
Created on: 29/Aug/18 07:30
Start Date: 29/Aug/18 07:30
Worklog Time Spent: 10m
Work Description: angoenka commented on a change in pull request #6278:
[BEAM-5239] Enable to configure latencyTrackingInterval
URL: https://github.com/apache/beam/pull/6278#discussion_r213568702
##
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 != -1) {
Review comment:
> 0 will be more explicit so lets go with that.
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:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 139144)
Time Spent: 1h 10m (was: 1h)
> 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 10m
> 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)
[jira] [Work logged] (BEAM-5239) Allow configure latencyTrackingInterval
[ https://issues.apache.org/jira/browse/BEAM-5239?focusedWorklogId=139133=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-139133 ] ASF GitHub Bot logged work on BEAM-5239: Author: ASF GitHub Bot Created on: 29/Aug/18 07:09 Start Date: 29/Aug/18 07:09 Worklog Time Spent: 10m Work Description: JozoVilcek commented on a change in pull request #6278: [BEAM-5239] Enable to configure latencyTrackingInterval URL: https://github.com/apache/beam/pull/6278#discussion_r213566671 ## File path: runners/flink/src/main/java/org/apache/beam/runners/flink/FlinkPipelineOptions.java ## @@ -167,4 +167,11 @@ Boolean isShutdownSourcesOnFinalWatermark(); void setShutdownSourcesOnFinalWatermark(Boolean shutdownOnFinalWatermark); + + @Description( + "Interval in milliseconds for sending latency tracking marks from the sources to the sinks.") + @Default.Long(-1L) + Long getLatencyTrackingInterval(); Review comment: I do not follow. I do not think it is debug option. For reference: https://github.com/apache/flink/blob/master/flink-core/src/main/java/org/apache/flink/api/common/ExecutionConfig.java#L244 Where do you suggest it to move? 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: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 139133) Time Spent: 50m (was: 40m) > 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: 50m > 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)
[jira] [Work logged] (BEAM-5239) Allow configure latencyTrackingInterval
[ https://issues.apache.org/jira/browse/BEAM-5239?focusedWorklogId=139134=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-139134 ] ASF GitHub Bot logged work on BEAM-5239: Author: ASF GitHub Bot Created on: 29/Aug/18 07:09 Start Date: 29/Aug/18 07:09 Worklog Time Spent: 10m Work Description: JozoVilcek commented on a change in pull request #6278: [BEAM-5239] Enable to configure latencyTrackingInterval URL: https://github.com/apache/beam/pull/6278#discussion_r213566671 ## File path: runners/flink/src/main/java/org/apache/beam/runners/flink/FlinkPipelineOptions.java ## @@ -167,4 +167,11 @@ Boolean isShutdownSourcesOnFinalWatermark(); void setShutdownSourcesOnFinalWatermark(Boolean shutdownOnFinalWatermark); + + @Description( + "Interval in milliseconds for sending latency tracking marks from the sources to the sinks.") + @Default.Long(-1L) + Long getLatencyTrackingInterval(); Review comment: I do not follow. I do not think it is debug option. More to allow/configure latency monitoring. For reference: https://github.com/apache/flink/blob/master/flink-core/src/main/java/org/apache/flink/api/common/ExecutionConfig.java#L244 Where do you suggest it to move? 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: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 139134) Time Spent: 1h (was: 50m) > 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 > 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)
[jira] [Work logged] (BEAM-5239) Allow configure latencyTrackingInterval
[
https://issues.apache.org/jira/browse/BEAM-5239?focusedWorklogId=139131=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-139131
]
ASF GitHub Bot logged work on BEAM-5239:
Author: ASF GitHub Bot
Created on: 29/Aug/18 07:07
Start Date: 29/Aug/18 07:07
Worklog Time Spent: 10m
Work Description: JozoVilcek commented on a change in pull request #6278:
[BEAM-5239] Enable to configure latencyTrackingInterval
URL: https://github.com/apache/beam/pull/6278#discussion_r213566235
##
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 != -1) {
Review comment:
latencyTrackingINteraval = 0 will disable the feature. This is what I need
(reason is `FLINK-10226`).
The idea is (taken from other options above), is user specify something,
forward it to flink. Reasonable values are `interval >= 0` but flink accepts
negative numbers and threat them as `0` = disable.
I can do `latencyTrackingInterval > 0` if you consider it more fit. Should I?
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:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 139131)
Time Spent: 40m (was: 0.5h)
> 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: 40m
> 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)
[jira] [Work logged] (BEAM-5239) Allow configure latencyTrackingInterval
[ https://issues.apache.org/jira/browse/BEAM-5239?focusedWorklogId=139035=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-139035 ] ASF GitHub Bot logged work on BEAM-5239: Author: ASF GitHub Bot Created on: 28/Aug/18 23:18 Start Date: 28/Aug/18 23:18 Worklog Time Spent: 10m Work Description: angoenka commented on a change in pull request #6278: [BEAM-5239] Enable to configure latencyTrackingInterval URL: https://github.com/apache/beam/pull/6278#discussion_r213502218 ## File path: runners/flink/src/main/java/org/apache/beam/runners/flink/FlinkPipelineOptions.java ## @@ -167,4 +167,11 @@ Boolean isShutdownSourcesOnFinalWatermark(); void setShutdownSourcesOnFinalWatermark(Boolean shutdownOnFinalWatermark); + + @Description( + "Interval in milliseconds for sending latency tracking marks from the sources to the sinks.") + @Default.Long(-1L) + Long getLatencyTrackingInterval(); Review comment: This looks like a global debug option and not a flink specific option. Lets move it to some thing like Tracking/PerformanceOption 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: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 139035) Time Spent: 0.5h (was: 20m) > 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: 0.5h > 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)
[jira] [Work logged] (BEAM-5239) Allow configure latencyTrackingInterval
[
https://issues.apache.org/jira/browse/BEAM-5239?focusedWorklogId=139036=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-139036
]
ASF GitHub Bot logged work on BEAM-5239:
Author: ASF GitHub Bot
Created on: 28/Aug/18 23:18
Start Date: 28/Aug/18 23:18
Worklog Time Spent: 10m
Work Description: angoenka commented on a change in pull request #6278:
[BEAM-5239] Enable to configure latencyTrackingInterval
URL: https://github.com/apache/beam/pull/6278#discussion_r213501162
##
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 != -1) {
Review comment:
nit: `latencyTrackingInterval > 0`
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:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 139036)
> 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: 0.5h
> 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)
[jira] [Work logged] (BEAM-5239) Allow configure latencyTrackingInterval
[ https://issues.apache.org/jira/browse/BEAM-5239?focusedWorklogId=138487=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-138487 ] ASF GitHub Bot logged work on BEAM-5239: Author: ASF GitHub Bot Created on: 27/Aug/18 17:30 Start Date: 27/Aug/18 17:30 Worklog Time Spent: 10m Work Description: apilloud commented on issue #6278: [BEAM-5239] Enable to configure latencyTrackingInterval URL: https://github.com/apache/beam/pull/6278#issuecomment-416303364 R: @angoenka @aljoscha 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: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 138487) Time Spent: 20m (was: 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: 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)
[jira] [Work logged] (BEAM-5239) Allow configure latencyTrackingInterval
[ https://issues.apache.org/jira/browse/BEAM-5239?focusedWorklogId=138396=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-138396 ] ASF GitHub Bot logged work on BEAM-5239: Author: ASF GitHub Bot Created on: 27/Aug/18 13:50 Start Date: 27/Aug/18 13:50 Worklog Time Spent: 10m Work Description: JozoVilcek opened a new pull request #6278: [BEAM-5239] Enable to configure latencyTrackingInterval URL: https://github.com/apache/beam/pull/6278 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: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 138396) Time Spent: 10m Remaining Estimate: 0h > 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: 10m > 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)
