Hey Ufuk, Thanks for the fast reply and fix! It's working now :)
Unfortunately the "other side" of the AbstractInvokable lifecycle is causing a bit of a trouble, as the AbstractInvokable does not wait for possible events before finishing, and it throws an IllegalStateException: Tried to send task event to producer before requesting a queue. exception when trying to send an event after the task finished. For now we have a workaround to this (the above fixed problem was the trickier one for us) in a higher level, but it would be nice if the events adjusted to the AbstractInvokable lifecycle, i.e. the AbstractInvokable would be kept up until all Readers/Writers that subscribed to events are shut down. Cheers, Gabor On Mon Feb 09 2015 at 5:59:19 PM Ufuk Celebi <u...@apache.org> wrote: > Hey Gabor, > > can you try this branch: https://github.com/uce/ > incubator-flink/tree/flink-1496-lost > > Is this working for you? > > This is a quick fix. It keeps track of events, which could not be > delivered to uninitialized channels and delivers them after they are > initialized. > > (The BufferReader, which does this, needs some refactoring. I think I blew > it up quite a bit when I "merged" it with the InputGate. I think I will > revert that soon.) > > On 09 Feb 2015, at 15:06, Hermann Gábor <reckone...@gmail.com> wrote: > > > Hi all, > > > > We've been trying to use events for two-way communication, but it seems > > like some of the backward events (at a BufferReader) are not sent at all > if > > the connection is not initialized yet (i.e. the given input channel is > > UNKNOWN). > > > > Is there a way to make sure the events get to the destination? > > > > Cheers, > > Gabor > >
