AM
To: user@flink.apache.org
Subject: Re: events eviction
Hi,
yes, in some cases it could be necessary. Could you maybe give some example of
what kind of window computation you want to achieve? Then we can see if it
would be possible without GlobalWindows and evictor.
Cheers,
Aljoscha
> On 15
ion, or dissemination)
> by persons other than the intended recipient(s) is prohibited. If you receive
> this e-mail in error, please notify the sender by phone or email immediately
> and delete it!
>
>
> -Original Message-----
> From: Aljoscha Krettek [mailto:aljos
and
delete it!
-Original Message-
From: Aljoscha Krettek [mailto:aljos...@apache.org]
Sent: Monday, February 15, 2016 11:58 AM
To: user@flink.apache.org
Subject: Re: events eviction
Hi,
you are right, the logic is in EvictingNonKeyedWindowOperator.emitWindow() for
non-parallel (non-k
Hi,
you are right, the logic is in EvictingNonKeyedWindowOperator.emitWindow() for
non-parallel (non-keyed) windows and in EvictingWindow.processTriggerResult()
in the case of keyed windows.
You are also right about the contract of the Evictor, it returns the number of
elements to be evicted fr
Hello,
I am looking over the mechanisms of evicting events in Flink. I saw that either
using a default evictor or building a custom one the logic is that the evictor
will provide the number of events to be discarded.
Could you please provide me with some additional pointers regarding the
mechan
