Thanx Max! Reza
On Wed, 29 May 2019, 16:38 Maximilian Michels, <m...@apache.org> wrote: > Hi Reza, > > The detailed view of the capability matrix states: "The Flink Runner > supports timers in non-merging windows." > > That is still the case. Other than that, timers should be working fine. > > > It makes very heavy use of Event.Time timers and has to do some manual > DoFn cache work to get around some O(heavy) issues. > > If you are running on Flink 1.5, timer deletion suffers from O(n) > complexity which has been fixed in newer versions. > > Cheers, > Max > > On 29.05.19 03:27, Reza Rokni wrote: > > Hi Flink experts, > > > > I am getting ready to push a PR around a utility class for > timeseries join > > > > left.timestamp match to closest right.timestamp where right.timestamp <= > > left.timestamp. > > > > It makes very heavy use of Event.Time timers and has to do some manual > > DoFn cache work to get around some O(heavy) issues. Wanted to test > > things against Flink: In the capability matrix we have "~" for Timer > > support in Flink: > > > > https://beam.apache.org/documentation/runners/capability-matrix/ > > > > Is that page outdated, if not what are the areas that still need to be > > addressed please? > > > > Cheers > > > > Reza > > > > > > -- > > > > This email may be confidential and privileged. If you received this > > communication by mistake, please don't forward it to anyone else, please > > erase all copies and attachments, and please let me know that it has > > gone to the wrong person. > > > > The above terms reflect a potential business arrangement, are provided > > solely as a basis for further discussion, and are not intended to be and > > do not constitute a legally binding obligation. No legally binding > > obligations will be created, implied, or inferred until an agreement in > > final form is executed in writing by all parties involved. > > >
