OK, I see. What information will be send out via the async request? Maybe you can fork of a separate stream with the info that needs to be send to the external service and later union the result with the main stream before the window operator?
Am Di., 23. Juli 2019 um 14:12 Uhr schrieb Flavio Pompermaier < pomperma...@okkam.it>: > The problem of bundling all records together within a window is that this > solution doesn't scale (in the case of large time windows and number of > events)..my requirement could be fulfilled by a keyed ProcessFunction but I > think AsyncDataStream should provide a first-class support to keyed streams > (and thus perform a single call per key and window..). What do you think? > > On Tue, Jul 23, 2019 at 12:56 PM Fabian Hueske <fhue...@gmail.com> wrote: > >> Hi Flavio, >> >> Not sure I understood the requirements correctly. >> Couldn't you just collect and bundle all records with a regular window >> operator and forward one record for each key-window to an AsyncIO operator? >> >> Best, Fabian >> >> Am Do., 18. Juli 2019 um 12:20 Uhr schrieb Flavio Pompermaier < >> pomperma...@okkam.it>: >> >>> Hi to all, >>> I'm trying to exploit async IO in my Flink job. >>> In my use case I use keyed tumbling windows and I'd like to execute the >>> async action only once per key and window (while >>> the AsyncDataStream.unorderedWait execute the async call for every element >>> of my stream) ..is there an easy way to do that apart from using a process >>> function (that basically will lose the asynchronicity)? >>> >>> Best, >>> Flavio >>> >> > >
