Re: [DISCUSS] Improving Trigger/Window API and Semantics

2016-03-22 Thread Aljoscha Krettek
Hi, I have some thoughts about Evictors as well yes, but I didn’t yet write them down. The basic idea about them is this: class Evictor { Predicate getPredicate(Iterable> elements, int size, W window); } class Predicate { boolean evict(StreamRecord element); } The evictor will return a pr

Re: [DISCUSS] Improving Trigger/Window API and Semantics

2016-03-22 Thread Fabian Hueske
Thanks for the write-up Aljoscha. I think it is a really good idea to separate the different aspects (fire, purging, lateness) a bit. At the moment, all of these need to be handled in the Trigger and a custom trigger is necessary whenever, you want some of these aspects slightly differently handled

Re: [DISCUSS] Improving Trigger/Window API and Semantics

2016-03-21 Thread Aljoscha Krettek
Hi, my previous message might be a bit hard to parse for people that are not very deep into the Trigger implementation. So I’ll try to give a bit more explanation right in the mail. The basic idea is that we observed some basic problems that keep coming up for people on the mailing lists and I

[DISCUSS] Improving Trigger/Window API and Semantics

2016-03-21 Thread Aljoscha Krettek
Hi, I’m also sending this to @user because the Trigger API concerns users directly. There are some things in the Trigger API that I think require some improvements. The issues are trigger testability, fire semantics and composite triggers and lateness. I started a document to keep track of thing