Hi Xu and Gabor,
I have not started the testing yet – it is high up on the list! I will share
anything I find when I get to it,
Kind regards, David.
From: Xu Huang
Date: Monday, 18 November 2024 at 03:47
To: dev@flink.apache.org
Subject: [EXTERNAL] Re: Flink V1 to V2 state migration
Hi
> Date: Monday, 11 November 2024 at 20:13
> To: dev@flink.apache.org
> Cc: Yuan Mei
> Subject: [EXTERNAL] Re: Flink V1 to V2 state migration
> Hi David,
>
> I think the first task would be to test and collect what is not working
> when migrating from 1.20 to 2.0-preview.
> To see su
adoption.
Thanks for your feedback,
Kind regards, David.
From: Gabor Somogyi
Date: Monday, 11 November 2024 at 20:13
To: dev@flink.apache.org
Cc: Yuan Mei
Subject: [EXTERNAL] Re: Flink V1 to V2 state migration
Hi David,
I think the first task would be to test and collect what is not
e should
> look at RockDB to forstdb state migration.
>
> WDYT?
>
>
> Kind regards, David.
>
>
>
>
> From: Zakelly Lan
> Date: Monday, 11 November 2024 at 09:31
> To: dev@flink.apache.org
> Subject: [EXTERNAL] Re: Flink V1 to V2 state migration
>
e migration where possible
3. Then to encourage adoption of forstdb state backend, then we should look
at RockDB to forstdb state migration.
WDYT?
Kind regards,David.
From: Zakelly Lan
Date: Monday, 11 November 2024 at 09:31
To: dev@flink.apache.org
Subject: [EXTERNAL] Re: Flink V1
Hi Alexis,
If you want to utilize the disaggregated state in Flink 2.0, you will need
to configure it to use the newly introduced ForSt Statebackend. We don't
support migrating states via checkpoints from one state backend to another.
However, it is possible to migrate state across state backends
Hi Zakelly,
For point 4, can you clarify two things:
- Is that incompatibility expected to be temporary, or will such a
migration never be possible?
- Will it be possible to configure the backend so that disaggregated state
is not used? I.e. keeping the current logic. And will this choice remain
Hi David and Galen,
To the best of my knowledge, the state or checkpoint itself has not changed
much (from 1.20 to 2.0), and will be compatible if you are using the same
statebackend. But there still some problems:
1. Due to numerous API breaking changes in 2.0, users may need to rewrite
their jo
Yes, I'd like to second that it would be very helpful to have a way to
migrate state from V1 to V2.
On Thu, Nov 7, 2024 at 12:11 PM David Radley
wrote:
> Hello,
> At Flink Forward I learnt that Fink V1 state could not be migrated to V2.
> I think this would be a big migration inhibitor for curre
Hello,
At Flink Forward I learnt that Fink V1 state could not be migrated to V2. I
think this would be a big migration inhibitor for current Flink users, as they
would need to throw away their existing state. As such I think this is a
critical possible blocking issue. Prior to Flink 2 going out,
10 matches
Mail list logo
