Re: Flink-Statefun : Design Solution advice ( ASYNC IO)

. They must finish before the Statefun runtime fails function invocation due to exceeded timeout. Best, Tymur Yarosh On 16 Aug 2022, 16:20 +0300, Himanshu Sareen , wrote: > Thanks, Tymor. I think the Datastream API job will also work for the > use-case. I'll try a quick POC. > >

Re: Flink-Statefun : Design Solution advice ( ASYNC IO)

the other one for acks from side output, and the last one for errors. Or you can even combine acks and errors to the same sink. Works for you? Best, Tymur Yarosh 16 серп. 2022 р., 13:40 +0300, Himanshu Sareen , писав(-ла): > Hi Tymur, > > 1. Why do you want a remote function to call an

Re: Flink-Statefun : Design Solution advice ( ASYNC IO)

Hi, Just a few questions: 1. Why do you want a remote function to call an embedded function in this case? 2. Do you have separate outgoing Kafka messages or join them per record? 3. What is explicit acknowledgment at the end for? Best, Tymur Yarosh 16 серп. 2022 р., 11:48 +0300, Himanshu Sareen

Re: Flink DataStream and remote Stateful Functions interoperability

Stateful Functions are in another repository. Take a look at device and phone packages. Deployment breaks into 2 parts: 1. Deploying your dataflow job (just a Flink cluster with your job running) 2. Deploying a service that implements remote functions as an ordinary service Best, Tymur Yarosh On

Re: Flink DataStream and remote Stateful Functions interoperability

Stateful Functions interoperability  https://medium.com/devoops-and-universe/realtime-detection-of-russian-crypto-phone-era-with-flink-datastream-and-stateful-functions-e77794fedc2a. Best, Tymur Yarosh On 24 May 2022, 21:16 +0300, Himanshu Sareen , wrote: > Team, > > I'm working

Introducing Statefun Tsukuyomi

. Please let me know if you find it useful. Pay attention that Docker is required. Kudos to the Flink team for the inspiration. Their approach to testing Stateful Functions inspired me to build this library. Check out the project page for more information:  https://github.com/4insyde/statefun-tsukuyomi Best, Tymur Yarosh

Re: Supporting different content-types such as String or JSON seems to always fail for me in Stateful Functions.

No problem, good luck with your learning journey! Best, Tymur Yarosh 17 квіт. 2022 р., 07:17 +0300, Marco Villalobos , писав(-ла): > You're right. I didn't notice that the ports were different. That was very > subtle. > > Thank you for pointing this out to me. I was s

Re: Supporting different content-types such as String or JSON seems to always fail for me in Stateful Functions.

example ports of functions server and the server that handles requests are different. Best, Tymur Yarosh 17 квіт. 2022 р., 04:17 +0300, Marco Villalobos , писав(-ла): > I'm sorry, I accidentally hit send before I was finished. > > Yes, I understand that Flink Stateful Functions ru

Re: Supporting different content-types such as String or JSON seems to always fail for me in Stateful Functions.

u can checkout the full example here  https://medium.com/devoops-and-universe/part-ii-building-next-gen-event-driven-application-powered-by-stateful-functions-a3139f299736 Best, Tymur Yarosh 14 квіт. 2022 р., 03:51 +0300, Marco Villalobos , писав(-ла): > I'm trying to write very simple

ClassCastException occurs when Flink DataStream sends a message to a remote stateful function

I. I believe this is the wrong usage of Stateful Function's SDK for Flink DataStream Integration. What is the correct way to implement Flink DataStream and remote Stateful Functions interoperability? The job is inspired by the official examples  https://nightlies.apache.org/flink/flink-statefun-docs-release-3.2/docs/sdk/flink-datastream/ Best, Tymur Yarosh