2020 03:21
> *To:* John Morrow ; user >
> *Subject:* Re: Stateful Functions + ML model prediction
>
> Hi John,
>
> It is definitely possible to use Apache Pulsar with StateFun. Could you
> open a JIRA ticket for that?
> It would be nice to see how much interest we can gathe
Morrow ; user
Subject: Re: Stateful Functions + ML model prediction
Hi John,
It is definitely possible to use Apache Pulsar with StateFun. Could you open a
JIRA ticket for that?
It would be nice to see how much interest we can gather on adding that as a new
IO module, and consider adding native
2020 11:37
> *To:* Igal Shilman
> *Cc:* user
> *Subject:* Re: Stateful Functions + ML model prediction
>
> Thanks very much Igal - that sounds like a good solution!
>
> I'm new to StateFun so I'll have to dig into it a bit more, but this
> sounds like a good direction.
>
n Morrow
Cc: user
Subject: Re: Stateful Functions + ML model prediction
Hi John,
Thank you for sharing your interesting use case!
Let me start from your second question:
Are stateful functions available to all Flink jobs within a cluster?
Yes, the remote functions are some logic exposed be
: user
Subject: Re: Stateful Functions + ML model prediction
Hi John,
Thank you for sharing your interesting use case!
Let me start from your second question:
Are stateful functions available to all Flink jobs within a cluster?
Yes, the remote functions are some logic exposed behind an HTTP endpoint
Hi John,
Thank you for sharing your interesting use case!
Let me start from your second question:
> Are stateful functions available to all Flink jobs within a cluster?
Yes, the remote functions are some logic exposed behind an HTTP endpoint,
and Flink would forward any message addressed to
Hi Flink Users,
I'm using Flink to process a stream of records containing a text field. The
records are sourced from a message queue, enriched as they flow through the
pipeline based on business rules and finally written to a database. We're using
the Ververica platform so it's running on
