Thanks everyone for the feedback.
I've just updated the status of Flink 1.11.3 earlier, in its corresponding
discussion thread [1].
>From the looks of it, it seems like it makes sense to proceed with StateFun
2.2.1 without waiting for Flink 1.11.3.
Since this is also the consensus we've reached h
Hi Gordon,
thanks a lot for this clarification.
In this case I would vote for releasing StateFun 2.2.1 asap and not wait
for 1.11.3.
Thanks a lot for your efforts!
On Tue, Nov 3, 2020 at 3:38 PM Tzu-Li (Gordon) Tai
wrote:
> Hi Robert,
>
> So far we've only seen a single user report the issue,
Hi Robert,
So far we've only seen a single user report the issue, but the severity of
FLINK-19692 is actually pretty huge.
TL;DR: If a checkpoint / savepoint that contains feedback events (which is
considered normal under typical StateFun operations) is attempted to be
restored from, the restore w
Thanks a lot for starting this thread.
How many users are affected by the problem? Is it somebody else besides the
initial issue reporter?
If it is just one person, I would suggest to rather help pushing the 1.11.3
release over the line or work on more StateFun features ;)
On Tue, Nov 3, 2020 at 1
Hi Gordon,
Thanks for driving this discussion!
I would go with the second suggestion - having two consecutive StateFun
releases 2.2.1 and 2.2.2, since the Flink-1.11.3 release
might take a while, and this hot-fix release is important enough to get out
as early as possible.
Cheers,
Igal.
On Mo
