Re: [ANNOUNCE] Apache Flink Stateful Functions Release 3.3.0 released

Thanks Martijn! On Tue, Sep 19, 2023 at 6:38 AM Martijn Visser wrote: > The Apache Flink community is excited to announce the release of > Stateful Functions 3.3.0! > > Stateful Functions is a cross-platform stack for building Stateful > Serverless applications, making it radically simpler to de

Re: [DISCUSS] Status of Statefun Project

; first place. > > re: paths for locating StateFun artifacts. > Can this be solved by simply passing in the path to the artifacts? As well > as the image tag for the locally build base StateFun image. They could > probably be environment variables. > > Cheers, > Gordon > &g

Re: [DISCUSS] Status of Statefun Project

jars + have a local base StateFun image. >2. Run the playground in "local" mode, so that it uses the local base >StateFun image + builds the playground code using copied artifact jars >(instead of pulling from Maven). > > That looks good to me! > > Thanks, &g

Re: [DISCUSS] Status of Statefun Project

k the CI manages this workflow. > > Thanks, > Gordon > > On Mon, Aug 14, 2023 at 10:42 AM Galen Warren > wrote: > > > I created a pull request for this: [FLINK-31619] Upgrade Stateful > > Functions to Flink 1.16.1 by galenwarren · Pull Request #331 · > > apac

Re: [DISCUSS] Status of Statefun Project

-statefun-playground. I can submit separate PR s those changes if everyone is on board. Also, should I plan to do the same upgrade to handle Flink 1.17.x? It should be easy to do, especially while the 1.16.x upgrade is fresh on my mind. Thanks. On Fri, Aug 11, 2023 at 6:40 PM Galen Warren wrote:

Re: [DISCUSS] Status of Statefun Project

ccurs in Docker containers. Gordon, is there a trick to running the sample code in flink-statefun-playground against yet-unreleased code that I'm missing? Thanks. On Sat, Jun 24, 2023 at 12:40 PM Galen Warren wrote: > Great -- thanks! > > I'm going to be out of town for about a

Re: [DISCUSS] Status of Statefun Project

> Martijn > > On Tue, Jun 20, 2023 at 2:21 PM Galen Warren > wrote: > >> Thanks. >> >> Martijn, to answer your question, I'd need to do a small amount of work >> to get a PR ready, but not much. Happy to do it if we're deciding to >> res

Re: [DISCUSS] Status of Statefun Project

that this is sufficient. > > Best, > Gordon > > On Thu, Jun 15, 2023 at 5:25 AM Martijn Visser > wrote: > >> Let me know if you have a PR for a Flink update :) >> >> On Thu, Jun 8, 2023 at 5:52 PM Galen Warren via user < >> user@flink.apac

Re: [DISCUSS] Status of Statefun Project

. you have to make it clear that your fork does not belong to the > >Apache Flink project. (Trademarks and all that) > > > > Neither should be significant hurdles (there should also be plenty of > > online resources regarding 1), and if you do this then you can freely >

Re: [DISCUSS] Status of Statefun Project

ged Martijn to take a look at this thread. > To my knowledge the project hasn't decided anything yet. > > On 27/05/2023 04:05, Galen Warren wrote: > > Ok, I get it. No interest. > > > > If this project is being abandoned, I guess I'll work with my own fork. > Is

Re: [DISCUSS] Status of Statefun Project

ijn said, let's be clear on what lies ahead (what option is finally > picked) and how to contribute (if possible) moving forward. > > Regards, > > Salva > > On Sat, May 27, 2023 at 4:05 AM Galen Warren via user < > user@flink.apache.org> wrote: > >> Ok, I ge

Re: [DISCUSS] Status of Statefun Project

Ok, I get it. No interest. If this project is being abandoned, I guess I'll work with my own fork. Is there anything I should consider here? Can I share it with other people who use this project? On Tue, May 16, 2023 at 10:50 AM Galen Warren wrote: > Hi Martijn, since you ope

Re: [DISCUSS] Status of Statefun Project

Hi Martijn, since you opened this discussion thread, I'm curious what your thoughts are in light of the responses? Thanks. On Wed, Apr 19, 2023 at 1:21 PM Galen Warren wrote: > I use Apache Flink for stream processing, and StateFun as a hand-off point >> for the rest of the appl

Re: [DISCUSS] Status of Statefun Project

> > I use Apache Flink for stream processing, and StateFun as a hand-off point > for the rest of the application. > It serves well as a bridge between a Flink Streaming job and > micro-services. This is essentially how I use it as well, and I would also be sad to see it sunsetted. It works well;

Re: [DISCUSS] Status of Statefun Project

Are there any next steps here? On Mon, Apr 3, 2023, 12:46 PM Galen Warren wrote: > Thanks for bringing this up. > > I'm currently using Statefun, and I've made a few small code contributions > over time. All of my PRs have been merged into master and most have been > re

Re: [DISCUSS] Status of Statefun Project

Thanks for bringing this up. I'm currently using Statefun, and I've made a few small code contributions over time. All of my PRs have been merged into master and most have been released, but a few haven't been part of a release yet. Most recently, I helped upgrade Statefun to be compatible with Fl

Re: question about Async IO

nce. >> >> We were also using reinterpretAsKeyedStream feature [1] after async >> operators to avoid calling ".keyBay" multiple times in pipeline. Calling >> .keyBy always has negative impact on performance. >> With reinterpretAsKeyedStream we were able to use

question about Async IO

I have a question about Flink's Async IO support: Async I/O | Apache Flink . I understand that access to state is not supported in an AsyncFunction. However, if the input to an AsyncFunction is a keyed st

question about Statefun/Flink version compatibility

The statefun project currently references Flink 1.13.2. Is 1.13.2 the *minimum *Flink version required, i.e. would Statefun be expected to work with Flink 1.14.2 or whatever the latest released version is, as well? Or is it important to use exactly version 1.13.2 of Flink? Thanks.