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 b
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 origi
> On Mon, Mar 7, 2022 at 5:50 PM Filip Karnicki
> wrote:
>
> > Hi, as far as I can tell, the way to provide a keystore/truststore
> password
> > to the kafka ingress/egress config is to put it in plaintext in
> > module.yaml, like so:
>
Hi, as far as I can tell, the way to provide a keystore/truststore password
to the kafka ingress/egress config is to put it in plaintext in
module.yaml, like so:
kind: io.statefun.kafka.v1/ingressspec: #(...) properties:-
ssl.truststore.password: changeme
This isn't ideal and I think it wou
Hi, we're having trouble running statefun jobs on a shared cloudera flink
cluster due to the presence of old protobuf-java classes on the classpath,
which don't work with statefun, causing MethodNotFound exceptions.
https://issues.apache.org/jira/browse/FLINK-26537
is to allow users to disable the
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 shar
ous 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?
> > > -
n to flink 1.16 when it's out
Kind regards
Fil
On Thu, 27 Oct 2022 at 10:02, Filip Karnicki
wrote:
> Hi All
>
> Our use case is that we need to process elements for the same key
> sequentially, and this processing involves async operations.
>
> If any part of the processing
