flink-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chesnay Schepler <ches...@apache.org>
Subject Re: Group already contains a Metric with the name 'latency'
Date Tue, 16 May 2017 12:43:19 GMT
Generally this isn't an issue; it only means that for some operators the 
latency metrics will not be available. The underlying issue is that the 
metric system has no way to differentiate operators except by their 
name; if the names are identical you end up with a collision.

If you're not using the latency metrics there's nothing to worry about. 
To prevent this warning from occurring you will have to give every 
operator a unique name.

On 16.05.2017 14:17, rizhashmi wrote:
>   i think i do have.
> In my implementation i am generating rollup for multiple timezone. So i took
> path of creating windows per timezone,  for each window separate instance of
> trigger created window with a new instance AssignerWithPunctuatedWatermarks
> & each time i applied same filter.
> Does this imply issue?
> --
> View this message in context: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Group-already-contains-a-Metric-with-the-name-latency-tp13157p13161.html
> Sent from the Apache Flink User Mailing List archive. mailing list archive at Nabble.com.

View raw message