[
https://issues.apache.org/jira/browse/FLINK-6545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16007785#comment-16007785
]
Xiaogang Shi commented on FLINK-6545:
-------------------------------------
I prefer not to use `SavepointSerializer` to serialize/deserialize external
checkpoints. Since the implementation of incremental checkpointing may vary a
lot in different state backends, it will be very tedious and error-prone for
`SavepointSerializer` to support each kind of incremental state handle.
Given that checkpoints are not supposed to be back-compatible, maybe we can
simply use java serializer to do the serialization of external checkpoints.
What do you think?
> Make incremental checkpoints externalizable
> -------------------------------------------
>
> Key: FLINK-6545
> URL: https://issues.apache.org/jira/browse/FLINK-6545
> Project: Flink
> Issue Type: Sub-task
> Components: State Backends, Checkpointing
> Affects Versions: 1.3.0
> Reporter: Stefan Richter
> Priority: Blocker
> Fix For: 1.3.0
>
>
> Incremental checkpoints are currently not externalizible. The missing piece
> is familiarizing the {{SavepointSerializer}}(s) with the new state handles
> classes that we added for incremental checkpointing. Currently, some of those
> (e.g.
> {{org.apache.flink.contrib.streaming.state.RocksDBIncrementalKeyedStateHandle}})
> currently live in the contrib.rocksdb package and need to be migrated. We
> can also push them to a different abstraction level, i.e.
> {{IncrementalKeyedStateHandle}} with some private data, referenced existing
> shared data (from previous checkpoints), and (presumably) newly created
> shared data (first created by the current checkpoint).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
