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 base here, I'm gradually getting ramped up on the Statefun code. I think there's two very useful bits in there that would be useful to bring into the Data Stream API.
The implementation behind the Embedded Module could serve as a foundation for a stateful keyed variant of the Async I/O functionality. This would open Data Stream up to new use cases like using Flink state as a read-through cache for an external data store (store results in Flink state with a ttl). Then, there's the "sink as a source" functionality. This would allow for cyclic streams without the need to write it out to another system. If both those capabilities existed in the Data Stream API, then Statefun could either become a much smaller project or eliminated as it wouldn't be too much work to wire some of these operators and a http client together to achieve something similar. Happy to hear any feedback about this option. I'd be interested in taking a stab at this if the core team would be open to accepting it. Andre On 2023/04/03 09:02:06 Martijn Visser wrote: > 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 help with the > maintenance of the project. > > In order to improve the situation, we need to solve the lack of committers > and the lack of contributors. > > On the lack of committers: > > 1. Ideally, there are some of the current Flink committers who have the > bandwidth and can help with reviewing PRs and merging them. > 2. If that's not an option, it could be a consideration that current > committers only approve and review PRs, that are approved by those who are > willing to contribute to Statefun and if the CI passes > > On the lack of contributors: > > 3. Next to having this discussion on the Dev and User mailing list, we can > also create a blog with a call for new contributors on the Flink project > website, send out some tweets on the Flink / Statefun twitter accounts, > post messages on Slack etc. In that message, we would inform how those that > are interested in contributing can start and where they could reach out for > more information. > > There's also option 4. where a group of interested people would split > Statefun from the Flink project and make it a separate top level project > under the Apache Flink umbrella (similar as recently has happened with > Flink Table Store, which has become Apache Paimon). > > If we see no improvements in the coming period, we should consider > sunsetting Statefun and communicate that clearly to the users. > > I'm looking forward to your thoughts. > > Best regards, > > Martijn > > [1] https://nightlies.apache.org/flink/flink-statefun-docs-master/ > [2] https://github.com/apache/flink-statefun >
