Yes .. is there any possibility access flink state variables in
WindowAssigner.assignWindows method?
--
View this message in context:
http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/State-in-Custom-Tumble-Window-Class-tp13177p13196.html
Sent from the Apache Flink User Maili
Thanks Walther,
I am not keeping my window forever.if the event is arrived after graced
period(lateness) i update event time to current time or say last event time.
That essentially solve infinite issue.
1.3 is not stable yet?
--
View this message in context:
http://apache-flink-user-maili
thanks Chesnay Schepler
--
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-tp13157p13178.html
Sent from the Apache Flink User Mailing List archive. mailing list archive at
Nabble.com.
i have requirement not to reject events .. even if they are late(after
maximum allowedness). So the way i achieve this but overriding Tumbling
window class and update event time to last event time if the event is late
and for identification attached additional column in db as
(currentevent/msPerHou
thanks for your reply
*latency* metrics appear to be pushed by AbstractStreamOperator.java
latencyGauge = this.metrics.gauge("latency", new LatencyGauge(historySize));
does it mean this methods need to be override?
--
View this message in context:
http://apache-flink-user-mailing-list-arch
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
I am getting bunch of warning in log files. Anyone help me sort out this
problem.
2017-04-28 00:20:57,947 WARN org.apache.flink.metrics.MetricGroup
- Name collision: Group already contains a Metric with the name 'latency'.
Metric will not be reported.[vpc2w2-rep-stage-
