Great, thanks
--
Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/
Thanks, that makes sense!
In addition, I've just found the reason for this in the code:
This is 1.5 (default value is 2000L):
https://github.com/apache/flink/blob/release-1.5/flink-core/src/main/java/org/apache/flink/configuration/MetricOptions.java#L109
This is 1.9 (default value is 0L)
https:/
Thanks for the response.
In 1.5 the docs also state that it should be enabled [1], however, it always
worked without setting latencyTrackingInterval
[1]
https://ci.apache.org/projects/flink/flink-docs-release-1.5/monitoring/metrics.html#latency-tracking
--
Sent from: http://apache-flink-user-m
Hi,
It's version 1.5.2.
I actually found the place in the code responsible for it.
In the "catch" block, it doesn't log the error and it lets it propagate.
https://github.com/apache/flink/blob/62839e88e15b338a8af9afcef698c38a194c592f/flink-connectors/flink-connector-kinesis/src/main/java/org/apa
This is great.
Can we have RSS feed for this?
Thanks
--
Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/
Elias Levy wrote
> Flink:
>
> Pros:
> * Intra-job traffic flows directly between workers.
> * More mature.
> * Higher-level constructs: SQL, CEP, etc.
How is SQL a Pro in Flink? Kafka Streams has KSQL which is at least as good
as Flink's SQL.
--
Sent from: http://apache-flink-user-mailing-l
I agree. At the moment deploying Flink to EMR is laborious and too custom. I
would like to know too.
--
Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/