It worked as expected.
One thing I also need to modify was the condition in onProcessingTime
and onElement
if (currentTime > nextFireTimestamp) {
to
if (currentTime >= nextFireTimestamp) {
Because there was a case when currentTime and nextFireTimestamp was
equal, so the trig
Aljoscha,
Thank you. That change looks good. I will try.
Regards,
Hironori
2016-03-31 22:20 GMT+09:00 Aljoscha Krettek :
> Oh I see what you mean now. I think the problem is that onProcessingTime
> changes nextFireTimestamp without actually setting a Trigger, as you said.
>
> I think changing on
Oh I see what you mean now. I think the problem is that onProcessingTime
changes nextFireTimestamp without actually setting a Trigger, as you said.
I think changing onProcessingTime to this should have the correct result:
@Override
public TriggerResult onProcessingTime(long time, W window, Trigge
Aljoscha,
Thanks for your response.
I understood that trigger is only set when new elements arrive, but in
my previous example, trigger fired at
20:51:40.002, then new element arrived at 20:51:41, 42, 43. So why
next trigger did not set at 20:51:45?
It looks like the following situation.
- 20:51:
Hi,
yes, right now this is expected behavior. But I see that it can be a bit,
well, unexpected.
The continuous trigger is only set when new elements arrive, so only when
you put new elements does the trigger fire again after five seconds. If you
want it to truly continuously fire every five secon
Hi
I noticed that ContinuousProcessingTimeTrigger sometimes does not fire.
I asked similar question before and applied this patch.
https://github.com/apache/flink/commit/607892314edee95da56f4997d85610f17a0dd470#diff-19bbcb3ea1403e483327408badfcd3f8
It looked work but still I have strange behavior
