Re: Maintaining watermarks per key, instead of per operator instance

2016-11-23 Thread Aljoscha Krettek
gt; .timeWindow(Time.hours(1)) > .allowedLateness(Time.hours(2)) > .apply(new ReadingAggregate(), new AggregateReadings(), new > AggregateReadings()); > > > > Feedback is very welcome. > > best, Stephan > > > > On 11 Nov 2016, at 00:29

Re: Maintaining watermarks per key, instead of per operator instance

2016-11-23 Thread kaelumania
.apply(new ReadingAggregate(), new AggregateReadings(), new >> AggregateReadings()); >> >> >> Feedback is very welcome. >> >> best, Stephan >> >> >> >> >>> On 11 Nov 2016, at 00:29, Fabian Hueske-2 [via Apache Flin

Re: Maintaining watermarks per key, instead of per operator instance

2016-11-23 Thread Aljoscha Krettek
> best, Stephan > > > > On 11 Nov 2016, at 00:29, Fabian Hueske-2 [via Apache Flink User Mailing > List archive.] <[hidden email] > <http://user/SendEmail.jtp?type=node&node=10179&i=0>> wrote: > > Hi Stephan, > > I just wrote an answer to your SO q

Re: Maintaining watermarks per key, instead of per operator instance

2016-11-21 Thread Stephan Epping
>> <http://user/SendEmail.jtp?type=node&node=10179&i=0>> wrote: >> > >> Hi Stephan, >> >> I just wrote an answer to your SO question. >> >> Best, Fabian > >> >> 2016-11-10 11:01 GMT+01:00 Stephan Epping <>

Re: Maintaining watermarks per key, instead of per operator instance

2016-11-21 Thread Aljoscha Krettek
e=10179&i=0>> wrote: > > Hi Stephan, > > I just wrote an answer to your SO question. > > Best, Fabian > > > 2016-11-10 11:01 GMT+01:00 Stephan Epping < href="x-msg://3/user/SendEmail.jtp?type=node&node=10033&i=0" > target="_top" re

Re: Maintaining watermarks per key, instead of per operator instance

2016-11-17 Thread kaelumania
e.] wrote: > > Hi Stephan, > > I just wrote an answer to your SO question. > > Best, Fabian > > 2016-11-10 11:01 GMT+01:00 Stephan Epping <[hidden email] > >: > Hello, > > I found this question in the Nabble archive > (http://apache-flink-user-mailin

Re: Maintaining watermarks per key, instead of per operator instance

2016-11-15 Thread Stephan Epping
hots? Will they work with the mentioned design? >> >> kind regards, >> Stephan > >>> On 11 Nov 2016, at 00:39, Fabian Hueske <>> href="x-msg://10/user/SendEmail.jtp?type=node&node=10094&i=1 >>> " >>> target="_top

Re: Maintaining watermarks per key, instead of per operator instance

2016-11-14 Thread Aljoscha Krettek
rwriteWatermarking()*... > per key? Or maybe using custom state plus a custom trigger? What happens if > a sensor dies or is being removed completely, how can this be detected as > watermarks would be ignored for window garbage collection. Or could we > dynamically schedule a job

Re: Maintaining watermarks per key, instead of per operator instance

2016-11-14 Thread kaelumania
<[hidden email] >> >: >> Hello, >> >> I found this question in the Nabble archive >> (http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Maintaining-watermarks-per-key-instead-of-per-operator-instance-tp7288.html >> >> <

Re: Maintaining watermarks per key, instead of per operator instance

2016-11-14 Thread Fabian Hueske
t;> >> I found this question in the Nabble archive ( >> http://apache-flink-user-mailing-list-archive.2336050.n4. >> nabble.com/Maintaining-watermarks-per-key-instead-of-per- >> operator-instance-tp7288.html) but was unable/dont know how to reply. >> >> Here is my que

Re: Maintaining watermarks per key, instead of per operator instance

2016-11-13 Thread Stephan Epping
an > > 2016-11-10 11:01 GMT+01:00 Stephan Epping <mailto:stephan.epp...@zweitag.de>>: > Hello, > > I found this question in the Nabble archive > (http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Maintaining-watermarks-per-key-instead-of-per-operator

Re: Maintaining watermarks per key, instead of per operator instance

2016-11-10 Thread Fabian Hueske
Hi Stephan, I just wrote an answer to your SO question. Best, Fabian 2016-11-10 11:01 GMT+01:00 Stephan Epping : > Hello, > > I found this question in the Nabble archive (http://apache-flink-user- > mailing-list-archive.2336050.n4.nabble.com/Maintaining- > watermarks-per-key

Re: Maintaining watermarks per key, instead of per operator instance

2016-11-10 Thread Stephan Epping
Hello, I found this question in the Nabble archive (http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Maintaining-watermarks-per-key-instead-of-per-operator-instance-tp7288.html <http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Maintaining-watermarks-

Re: Maintaining watermarks per key, instead of per operator instance

2016-06-04 Thread Aljoscha Krettek
Hi, I think you first have to convert back to a DataStream using .select() or .flatSelect(). But Till should know more about this, maybe he can help. Cheers, Aljoscha On Thu, 2 Jun 2016 at 19:19 Kanstantsin Kamkou wrote: > Hi Aljoscha! Is it possible somehow to use the RichXFunction in CEP? > T

Re: Maintaining watermarks per key, instead of per operator instance

2016-06-02 Thread Kanstantsin Kamkou
Hi Aljoscha! Is it possible somehow to use the RichXFunction in CEP? The task is pretty similar, but I have to ignore once the next triggered event for the same key. On Wed, Jun 1, 2016 at 2:54 PM, Aljoscha Krettek wrote: > Hi, > yeah, in that case per-key watermarks would be useful for you. I w

Re: Maintaining watermarks per key, instead of per operator instance

2016-06-02 Thread leon_mclare
Hi again Aljoscha, understood. Thanks for the link. I really like the straightforward approach concerning storing state. It makes things very easy. The improvements are very interesting, particularly the composite triggers. That would significantly improve flexibility. Kind regards Leon 1. Ju

Re: Maintaining watermarks per key, instead of per operator instance

2016-06-01 Thread Aljoscha Krettek
Hi, yeah, in that case per-key watermarks would be useful for you. I won't be possible to add such a feature, though, due to the (possibly) dynamic nature of the key space and how watermark tracking works. You should be able to implement it with relatively low overhead using a RichFlatMapFunction

Re: Maintaining watermarks per key, instead of per operator instance

2016-05-31 Thread leon_mclare
Hi Aljoscha, thanks for the speedy reply. I am processing measurements delivered by smart meters. I use windows to gather measurements and calculate values such as average consumption. The key is simply the meter ID. The challenge is that meters may undergo network partitioning, under which t

Re: Maintaining watermarks per key, instead of per operator instance

2016-05-31 Thread Aljoscha Krettek
Hi, I'm afraid this is impossible with the current design of Flink. Might I ask what you want to achieve with this? Maybe we can come up with a solution. -Aljoscha On Tue, 31 May 2016 at 13:24 wrote: > My use case primarily concerns applying transformations per key, with the > keys remaining fi

Maintaining watermarks per key, instead of per operator instance

2016-05-31 Thread leon_mclare
My use case primarily concerns applying transformations per key, with the keys remaining fixed throughout the topology. I am using event time for my windows. The problem i am currently facing is that watermarks in windows propagate per operator instance, meaning the operator event time increase