Re: IterativeStream seems to ignore maxWaitTimeMillis

2016-11-23 Thread Juan Rodríguez Hortalá
Thanks a lot for your suggestion Aljoscha, it has helped me discovered the problem: I was using an Executor inside a RichFunction and I wasn't shutting down the executor. Now I call executor.shutdownNow() in RichFunction .close(), and the job stops when both the input and the loop are exhausted. G

Re: IterativeStream seems to ignore maxWaitTimeMillis

2016-11-23 Thread Aljoscha Krettek
Ah, cancel() won't be called on the source if it is already stopped, I think. Could you try boiling it down to the very basics, i.e. have just the source and an iteration and check what happens. On Wed, 23 Nov 2016 at 05:08 Juan Rodríguez Hortalá < juan.rodriguez.hort...@gmail.com> wrote: > Thank

Re: IterativeStream seems to ignore maxWaitTimeMillis

2016-11-22 Thread Juan Rodríguez Hortalá
Thanks for your answer Aljoscha, The source stops, when I comment all the transformed streams and just print the input, the program completes. But this is custom SourceFunction, could this be related to this? Maybe I should implement emitWatermark? I'm using ingestion time so I assumed this wasn't

Re: IterativeStream seems to ignore maxWaitTimeMillis

2016-11-21 Thread Aljoscha Krettek
Might it be that your initial source never stops? A loop will only terminate if both the original source stops and the loop timeout is reached. On Mon, 21 Nov 2016 at 07:58 Juan Rodríguez Hortalá < juan.rodriguez.hort...@gmail.com> wrote: > Hi, > > I wrote a proof of concept for a Java version of