>>>> > >>>>>>
> > >> > >>>> > >>>>>> Our use case is that we need to process elements for
> the
> > >> same
> > >> > >>>> key
> > >> > >>>>
t; > >>>>> wrote:
> >> > >>>> > >>>>>
> >> > >>>> > >>>>>> Hi All
> >> > >>>> > >>>>>>
> >> > >>>> > >>>>>> Our use case is that we need
t; >>>>>>
>> > >>>> > >>>>>> Our use case is that we need to process elements for the
>> same
>> > >>>> key
>> > >>>> > >>>>>> sequentially, and this processing involves async
>> o
ges for that key, until a retry succeeds or a
> > >>>> human
> > >>>> > sends a
> > >>>> > >>>>>> 'skip' command message.
> > >>>> > >>>>>>
> > >>>
age.
> >>>> > >>>>>>
> >>>> > >>>>>> diagram:
> >>>> > >>>>>>
> >>>> >
> >>>>
> https://mermaid.live/edit#pako:eNplkL1uwzAMhF-F0JQADrp76FR06tSOcQfWom3V-nFFqoUR591L20mXaqAOxHd3AC-mTZ
aU6u0mMfGNPGqHBZJb1piasmFKlMmqxd7cqj3Dqbu0DNdfwHTGoek
>>>> > >>>>>> mermaid (in case mermaid.live goes down in the future):
>>>> > >>>>>> graph LR
>>>> > >>>>>> incoming[incoming events
the future):
>>> > >>>>>> graph LR
>>> > >>>>>> incoming[incoming events] --> job(Flink statefun job)
>>> > >>>>>> commands[commands] -->|skip| job
>>> > >>>>>> job --> |sequentially per key| remote(remote
t;>>> systems)
>> > >>>>>>
>> > >>>>>> Having the processing happen outside of Flink is nice-to-have
>> from
>> > an
>> > >>>>>> independent scalability point of view, but is not strictly
>> required.
>> > &
aging, but also no way I can
> > >>>>>> think of to use existing native Flink operators like async i/o
> > (which when
> > >>>>>> I last checked a few years back didn't have access to keyed state)
> > >>>>>>
> > >>>>>&g
years back didn't have access to keyed state)
> >>>>>>
> >>>>>>
> >>>>>> P.S. Please note that there is already a pull request that has
> >>>>>> something to do wtih Flink 1.15, albeit wi
have access to keyed state)
>>>>>>
>>>>>>
>>>>>> P.S. Please note that there is already a pull request that has
>>>>>> something to do wtih Flink 1.15, albeit without a description or a jira:
>>>>>> https://github.com/apache/fl
> On Wed, 26 Oct 2022 at 19:54, Galen Warren
>>>>> wrote:
>>>>>
>>>>>> Hi Gordon (and others),
>>>>>>
>>>>>> I'm also using this project for stateful messaging, including
>>>>>> messaging
>>>>>&
Warren
>>>> wrote:
>>>>
>>>>> Hi Gordon (and others),
>>>>>
>>>>> I'm also using this project for stateful messaging, including messaging
>>>>> among functions.
>>>>>
>>>>> I'
uding messaging
>>>> among functions.
>>>>
>>>> I've contributed a small amount of code in the past and have also
>>>> enabled
>>>> Flink 1.15 compatibility in a local fork, so I might be able to help out
>>>> here.
t; Galen
>>>
>>> On Wed, Oct 26, 2022 at 1:34 PM Ken Krugler >> >
>>> wrote:
>>>
>>> > Hi Gordon,
>>> >
>>> > We’re using it for stateful messaging, and also calling remote
>>> > Python-based functions.
&g
at 1:34 PM Ken Krugler
>> wrote:
>>
>> > Hi Gordon,
>> >
>> > We’re using it for stateful messaging, and also calling remote
>> > Python-based functions.
>> >
>> > So yes, also very interested in what is going to happen with the this
> > — Ken
> >
> >
> >
> > > Begin forwarded message:
> > >
> > > From: "Tzu-Li (Gordon) Tai"
> > > Subject: Re: Stateful Functions with Flink 1.15 and onwards
> > > Date: October 26, 2022 at 10:25:26 AM PDT
> >
gt;
>
> > Begin forwarded message:
> >
> > From: "Tzu-Li (Gordon) Tai"
> > Subject: Re: Stateful Functions with Flink 1.15 and onwards
> > Date: October 26, 2022 at 10:25:26 AM PDT
> > To: dev@flink.apache.org
> > Reply-To: dev@flink.apache.org
> >
Subject: Re: Stateful Functions with Flink 1.15 and onwards
> Date: October 26, 2022 at 10:25:26 AM PDT
> To: dev@flink.apache.org
> Reply-To: dev@flink.apache.org
>
> Hi Filip,
>
> Thanks for bringing this up.
>
> The hard truth is that committers who were previously acti
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
As far as I know the original authors are not working on this
implementation anymore. Other folks might be able to provide more context.
Instead of rewriting your code to be a native Flink job, would it be an
option for your team to pick up the pull request to port statefun to Flink
1.15?
-Max
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
22 matches
Mail list logo
