Re: Signal Trigger

Hi, I believe this "timestamp + this.delay" is the signal event timestamp + the allowed lateness which in this case an configuring it as EventTimeSessionSignalTrigger.of(this.lateness.toMilliseconds()); So, if the allowed lateness is 10 seconds and the event arrived at 15:10 the event timer would

回复：PartitionNotFoundException on deploying streaming job

Hi Kamil,       When the producer receives the PartitionRequest from downstream task, first it will check whether the requested partition is already registered. If not, it will reponse PartitionNotFoundException.And the upstream task is submitted and begins to run, it will registered all its par

Re: Signal Trigger

Hi, this looks almost correct. In your written description you say that the Trigger should fire after the allowed lateness if a signal event was received. In your code, however, you fire at the timestamp of the signal event. Best, Aljoscha > On 3. Apr 2017, at 18:45, nragon wrote: > > Hi Steph

Re: concurrency?

Hi, just a bit of clarification. In the example above: time = 1, processElement(A) -> put A in state keyed to t=1, registerProcTimer(2) time = 1, processElement(B) -> put B in state keyed to t=1, registerProcTimer(2) // deduplicated time = 2, onTimer(2) -> access state with key t=2-1, get A, B ti

Re: Cogrouped Stream never triggers tumbling event time window

Hi, thanks for letting us know! And sorry that you didn’t get any response from the community, I myself just got back from vacation so I’m only now catching up on mail. Best, Aljoscha > On 30. Mar 2017, at 18:24, Andrea Spina wrote: > > Dear community, > > I finally solved the issue i was bum

Flink Cross Strategies

Hi, I would like to knot how the Flink cross function works. I found that there are four strategies ( NESTEDLOOP_BLOCKED_OUTER_FIRST, NESTEDLOOP_BLOCKED_OUTER_SECOND, NESTEDLOOP_STREAMED_OUTER_FIRST, NESTEDLOOP_STREAMED_OUTER_SECOND), but I need some more detailed explanations please. Thank

PartitionNotFoundException on deploying streaming job

Hi guys, When I run my streaming job I almost always have initially PartitionNotFoundException. Job fails, after that restarts and it runs ok. I wonder what is causing that and if I can adjust some parameters to not have this initial failure. I have flink session on yarn with 55 task managers. 4

Re: In-Memory data grid

My concern and my requirements are that the cache must be shared with other jobs or any other application. If a user or job changes the value in ignite, it must be updated in every flink job it uses that cache. Thanks -- View this message in context: http://apache-flink-user-mailing-list-archi