Hello Aljoscha and Hironori,
Nice initiative! I totally agree with the proposals in the document.
I also left some comments and I will soon start working on some
of the issues there.
Kostas
> On Mar 25, 2016, at 12:53 PM, Hironori Ogibayashi
> wrote:
>
> Aljoscha,
>
> Yes, it's reproducibl
Aljoscha,
Yes, it's reproducible as long as I tried. Here is the code and
procedure: https://gist.github.com/ogibayashi/402153bcd79138c35d6a
Thank you for your explanation about the removal of windows. I didn't
know that calling .trigger() will replace default
window trigger.
I have read your doc
Hi,
the output at 19:44:44.635 is indeed strange. Is this reproducible?
As for the removal of windows. That is a pitfall a lot of users have fallen
into. The timeWindowAll() call just sets up a window assigner, so in your case
the equivalent call would be:
.flatMap { _.toLowerCase.split("\
Aljoscha,
Thank you for fixing the issue.
I built both Flink server and job with the code you provided, and it
worked as almost expected.
The output was below. I am wondering why the value emitted at
19:44:44.635 while I set
ContinuousProcessingTimeTrigger.of(Time.seconds(5)), but it's not a
probl
Hi,
I’m afraid you discovered a bug in the ContinuousProcessingTimeTrigger. The
timer is not correctly set. You can try it with this fixed version, that I will
also update in the Flink code:
https://gist.github.com/aljoscha/cbdbd62932b6dd2d1930
One more thing, the ContinuousProcessingTimeTrigge
