Thank you,
i will study that. it is a bit more raw i would say. The thing is my source
is Kafka. I will have to see how to combine all of that altogether in the
most elegant way possible. Will get back to you on this, after i scratch my
head enough.
Best,
Daniel
On Wed, May 25, 2016 at 11:02 AM
I see what you mean now. The Akka Streams API is very interesting, in how
they allow async calls.
For Flink, I think you could implement it as a custom source that listens
for the change stream, starts futures to get data from the database and
emits elements when the future completes. I quickly sk
Maybe the following can illustrate better what i mean
http://doc.akka.io/docs/akka/2.4.6/scala/stream/stream-integrations.html#Integrating_with_External_Services
On Wed, May 25, 2016 at 5:16 AM, Aljoscha Krettek
wrote:
> Hi,
> there is no functionality to have asynchronous calls in user function
Thank you for your answer.
Maybe I should have mentioned that I am at the beginning with both
framework, somewhat making a choice by evaluating their capability. I know
Akka stream better.
So my question would be simple. Let say that
1-/ have a stream of event that are simply information about t
Hi,
there is no functionality to have asynchronous calls in user functions in
Flink.
The asynchronous action feature in Spark is also not meant for such things,
it is targeted at programs that need to pull all data to the application
master. In Flink this is not necessary because you can specify a
I'm looking for a way to avoid thread starvation in my tasks, by returning
future but i don't see how is that possible.
Hence i would like to know, how flink handle the case where in your job you
have to perform network calls (I use akka http or spray) or any IO
operation and use the result of it.
