Re: [DISCUSS] Status of Statefun Project

Hi Gordon Any chance we could get this reviewed and released to the central repo? We're currently forced to use a Flink version that has a nasty bug causing an operational nightmare Many thanks Fil On Sat, 19 Aug 2023 at 01:38, Galen Warren via user wrote: > Gotcha, makes sense as to the

Re: [DISCUSS] Status of Statefun Project

Gotcha, makes sense as to the original division. >> Can this be solved by simply passing in the path to the artifacts This definitely works if we're going to be copying the artifacts on the host side -- into the build context -- and then from the context into the image. It only gets tricky to

Re: [DISCUSS] Status of Statefun Project

Hi Galen, The original intent of having a separate repo for the playground repo, was that StateFun users can just go to that and start running simple examples without any other distractions from the core code. I personally don't have a strong preference here and can understand how it would make

Re: [DISCUSS] Status of Statefun Project

Yes, exactly! And in addition to the base Statefun jars and the jar for the Java SDK, it does an equivalent copy/register operation for each of the other SDK libraries (Go, Python, Javascript) so that those libraries are also available when building the playground examples. One more question: In

Re: [DISCUSS] Status of Statefun Project

Hi Galen, > locally built code is copied into the build containers so that it can be accessed during the build. That's exactly what we had been doing for release testing, yes. Sorry I missed that detail in my previous response. And yes, that sounds like a reasonable approach. If I understand

Re: [DISCUSS] Status of Statefun Project

Thanks. If you were to build a local image, as you suggest, how do you access that image when building the playground images? All the compilation of playground code happens inside containers, so local images on the host aren't available in those containers. Unless I'm missing something? I've

Re: [DISCUSS] Status of Statefun Project

Hi Galen, > Gordon, is there a trick to running the sample code in flink-statefun-playground against yet-unreleased code that I'm missing? You'd have to locally build an image from the release branch, with a temporary image version tag. Then, in the flink-statefun-playground, change the image

Re: [DISCUSS] Status of Statefun Project

I created a pull request for this: [FLINK-31619] Upgrade Stateful Functions to Flink 1.16.1 by galenwarren · Pull Request #331 · apache/flink-statefun (github.com) . JIRA is here: [FLINK-31619] Upgrade Stateful Functions to Flink 1.16.1 - ASF

Re: [DISCUSS] Status of Statefun Project

I'm done with the code to make Statefun compatible with Flink 1.16, and all the tests (including e2e succeed). The required changes were pretty minimal. I'm running into a bit of a chicken/egg problem executing the tests in flink-statefun-playground

Re: [DISCUSS] Status of Statefun Project

This is great news, as we're using statefun as well. Please don't hesitate to let me know if you need me to do some additional testing on a real life prod-like setup. On Sat, 24 Jun 2023 at 18:41, Galen Warren via user wrote: > Great -- thanks! > > I'm going to be out of town for about a week

Re: [DISCUSS] Status of Statefun Project

Great -- thanks! I'm going to be out of town for about a week but I'll take a look at this when I'm back. On Tue, Jun 20, 2023 at 8:46 AM Martijn Visser wrote: > Hi Galen, > > Yes, I'll be more than happy to help with Statefun releases. > > Best regards, > > Martijn > > On Tue, Jun 20, 2023 at

Re: [DISCUSS] Status of Statefun Project

Hi Galen, Yes, I'll be more than happy to help with Statefun releases. Best regards, 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

Re: [DISCUSS] Status of Statefun Project

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 restart Statefun releases -- are we? -- Galen On Sat, Jun 17, 2023 at 9:47 AM Tzu-Li (Gordon) Tai wrote: > > Perhaps he could weigh in on

Re: [DISCUSS] Status of Statefun Project

> Perhaps he could weigh in on whether the combination of automated tests plus those smoke tests should be sufficient for testing with new Flink versions What we usually did at the bare minimum for new StateFun releases was the following: 1. Build tests (including the smoke tests in the e2e

Re: [DISCUSS] Status of Statefun Project

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 wrote: > Thanks Martijn. > > Personally, I'm already using a local fork of Statefun that is compatible > with Flink 1.16.x, so I wouldn't have any need for a released version > compatible

Re: [DISCUSS] Status of Statefun Project

Why can't the Apache Software Foundation allow community members to bring it up to date? What's the process for that? I believe that there are people and companies on this mailing list interested in supporting Apache Flink Stateful Functions. You already had two people on this thread express

Re: [DISCUSS] Status of Statefun Project

Thanks Martijn. Personally, I'm already using a local fork of Statefun that is compatible with Flink 1.16.x, so I wouldn't have any need for a released version compatible with 1.15.x. I'd be happy to do the PRs to modify Statefun to work with new versions of Flink as they come along. As for

Re: [DISCUSS] Status of Statefun Project

Hi all, Apologies for the late reply. I'm willing to help out with merging requests in Statefun to keep them compatible with new Flink releases and create new releases. I do think that validation of the functionality of these releases depends a lot on those who do these compatibility updates,

Re: [DISCUSS] Status of Statefun Project

Thanks for the information. On Tue, Jun 6, 2023, 6:07 AM Chesnay Schepler wrote: > If you were to fork it /and want to redistribute it/ then the short > version is that > > 1. you have to adhere to the Apache licensing requirements > 2. you have to make it clear that your fork does not belong

Re: [DISCUSS] Status of Statefun Project

If you were to fork it /and want to redistribute it/ then the short version is that 1. you have to adhere to the Apache licensing requirements 2. 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

Re: [DISCUSS] Status of Statefun Project

Getting to a resolution here would be great and much appreciated, yes. On Sat, May 27, 2023 at 1:03 AM Salva Alcántara wrote: > Hey Galen, > > I took a look at StateFun some time ago; not using it in production but I > agree that it would be a pity to abandon it. > > As Martijn said, let's be

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 opened this

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 application. >> It

RE: [DISCUSS] Status of Statefun Project

Hey all, I share the same sentiment as others here. It would be a shame if statefun went away. At the very least, it would be nice to see it go into maintenance mode just to maintain compatibility with Flink releases. I do come with a different proposal though. Feel free to let me know if I'm off

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

I am currently using Stateful Functions in my application. 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. I would be disappointed if StateFun was sunsetted.

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 > released, but a few haven't

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

[DISCUSS] Status of Statefun Project

Hi everyone, I want to open a discussion on the status of the Statefun Project [1] in Apache Flink. As you might have noticed, there hasn't been much development over the past months in the Statefun repository [2]. There is currently a lack of active contributors and committers who are able to