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?
[ Full content available at: https://github.com/apache/beam/pull/6278 ] This message was relayed via gitbox.apache.org for [email protected]
