Hi Filip, Thanks for bringing this up.
The hard truth is that committers who were previously active on the StateFun subproject, including myself, all currently have other focuses. Indeed, we may need to discuss with the community on how to proceed if there seems to be no continued committer coverage. If it's just a matter of upgrading the supported Flink version, I'm still familiar enough with the subproject to probably be able to drive this (or if your team is up to it, I can assist you on that). For the long-term, as a data point I'm curious to see how many users are using StateFun in production today, and how you're using it? - Do your applications have arbitrary / cyclic / bi-directional messaging between individual functions? - Or are you utilizing StateFun simply to allow your stateful functions to run remotely as separate processes? If the majority is only the latter category, there might be a case to support remote functions natively in Flink (which has been a discussion in the past). Thanks, Gordon On Wed, Oct 26, 2022 at 3:30 AM Filip Karnicki <filip.karni...@gmail.com> wrote: > Hi, I noticed that the development on stateful functions has come to a bit > of a halt, with a pull request to update statefun to use Flink 1.15 being > in the `open` state since May 2022. > > What do we think is the future of this sub-project? > > The background to this question is that my team is on a shared Flink > cluster which will soon be upgrading to Flink 1.15. If I need to re-write > all our code as a native Flink job (rather than a remote stateful function) > then I need to get started right away. > > Many thanks, > Fil >
