Re: Flink event processing immediate feedback

2016-04-14 Thread Igor Berman
Yes, indeed this is direction we are trying currently thanks On 14 April 2016 at 18:31, Aljoscha Krettek wrote: > Could still be, as I described it by using a message queue to do the > communication between Flink and the front end. > > On Thu, 14 Apr 2016 at 17:30 Igor Berman wrote: > >> Hi A

Re: Flink event processing immediate feedback

2016-04-14 Thread Aljoscha Krettek
Could still be, as I described it by using a message queue to do the communication between Flink and the front end. On Thu, 14 Apr 2016 at 17:30 Igor Berman wrote: > Hi Aljoscha, > thanks for the response > > Synchronous - in our case means that request by end-client to frontend(say > some REST

Re: Flink event processing immediate feedback

2016-04-14 Thread Igor Berman
Hi Aljoscha, thanks for the response Synchronous - in our case means that request by end-client to frontend(say some REST call) needs to wait until processing in backend(Flink) is done and should return response(e.g. alert) back to end-client(i.e. end-client -> frontend -> kafka-> flink) those req

Re: Flink event processing immediate feedback

2016-04-14 Thread Aljoscha Krettek
Hi, what do you mean by "synchronous". If I understood it correctly then some events entering the Flink pipeline would trigger an alert while some others would not trigger an alert. How would the component that receives such alerts know when to wait and when to don't wait. As I see it you can pus