Re: [Stateful Functions] Help for calling remote stateful function (written in Python)

2021-04-29 Thread Igal Shilman
Hi Bonino, What you are experiencing is "expected" the situation is that the finite streaming job is completing too fast. StateFun is designed to run continuously, and fault tolerance and corrections is achieved by checkpointing its internal state into a durable storage. You can verify this by

Re: [Stateful Functions] Help for calling remote stateful function (written in Python)

2021-04-28 Thread Bonino Dario
Dear Igal, dear List Thank you very much for your reply. Your advice was crucial to overcome the issue. I have now created a TypedValue manually and successfully managed to communicate with the remote function in Python. Nevertheless, I am still facing a strange behavior regarding the

Re: [Stateful Functions] Help for calling remote stateful function (written in Python)

2021-04-27 Thread Igal Shilman
Hello! Your analysis is correct, indeed what is passed is whatever is being handed to withMessageBody(..). Starting with StateFun 3.0, if you need to send a message to a remote function the message needs to be a TypedValue. You can create an instance of TypedValue manually, or you can add a

[Stateful Functions] Help for calling remote stateful function (written in Python)

2021-04-27 Thread Bonino Dario
Dear List, I am trying to call a sample stateful function defined in Python, using the Stateful Function Python SDK, from a Flink pipeline. I am building upon the examples provided for theĀ  SDK for Flink DataStream Integration but I am currently stuck on a type cast issue that I am not able