Hi, 15725139602 Please send email to dev-unsubscr...@flink.apache.org if you want to unsubscribe the mail from dev <dev@flink.apache.org>, and you can refer[1] for more details.
Best, Leonard [1]https://flink.apache.org/community.html#mailing-lists > 2022年10月31日 下午6:02，m15725139602 <15725139...@163.com> 写道： > > unsubscribe > > > > | | > 15725139...@163.com > | > | > 邮箱：15725139...@163.com > | > > > > > ---- Replied Message ---- > | From | Piotr Nowojski (Jira)<j...@apache.org> | > | Date | 10/31/2022 17:55 | > | To | dev@flink.apache.org<dev@flink.apache.org> | > | Cc | | > | Subject | [jira] [Created] (FLINK-29807) Drop TypeSerializerConfigSnapshot > and savepoint support from Flink versions < 1.8.0 | > Piotr Nowojski created FLINK-29807: > -------------------------------------- > > Summary: Drop TypeSerializerConfigSnapshot and savepoint support > from Flink versions < 1.8.0 > Key: FLINK-29807 > URL: https://issues.apache.org/jira/browse/FLINK-29807 > Project: Flink > Issue Type: Improvement > Components: Runtime / Checkpointing > Affects Versions: 1.17 > Reporter: Piotr Nowojski > Assignee: Piotr Nowojski > Fix For: 1.17 > > > The motivation behind this move is two fold. One reason is that it > complicates our code base unnecessarily and creates confusion on how to > actually implement custom serializers. The immediate reason is that I wanted > to clean up Flink's configuration stack a bit and refactor the > ExecutionConfig class [2]. This refactor would keep the API compatibility of > the ExecutionConfig, but it would break savepoint compatibility with > snapshots written with some of the old serializers, which had ExecutionConfig > as a field and were serialized in the snapshot. This issue has been resolved > by the introduction of TypeSerializerSnapshot in Flink 1.7 [3], where > serializers are no longer part of the snapshot. > > TypeSerializerConfigSnapshot has been deprecated and no longer used by > built-in serializers since Flink 1.8 [4] and [5]. Users were encouraged to > migrate to TypeSerializerSnapshot since then with their own custom > serializers. That has been plenty of time for the migration. > > This proposal would have the following impact for the users: > 1. we would drop support for recovery from savepoints taken with Flink < > 1.7.0 for all built in types serializers > 2. we would drop support for recovery from savepoints taken with Flink < > 1.8.0 for built in kryo serializers > 3. we would drop support for recovery from savepoints taken with Flink < 1.17 > for custom serializers using deprecated TypeSerializerConfigSnapshot > > 1. and 2. would have a simple migration path. Users migrating from those old > savepoints would have to first start his job using a Flink version from the > [1.8, 1.16] range, and take a new savepoint that would be compatible with > Flink 1.17. > 3. This is a bit more problematic, because users would have to first migrate > their own custom serializers to use TypeSerializerSnapshot (using a Flink > version from the [1.8, 1.16]), take a savepoint, and only then migrate to > Flink 1.17. However users had already 4 years to migrate, which in my opinion > has been plenty of time to do so. > > *As discussed and vote is currently in progress*: > https://lists.apache.org/thread/x5d0p08pf2wx47njogsgqct0k5rpfrl4 > > > > -- > This message was sent by Atlassian Jira > (v8.20.10#820010)
