[ 
https://issues.apache.org/jira/browse/FLINK-6600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tzu-Li (Gordon) Tai updated FLINK-6600:
---------------------------------------
    Description: 
Currently, only the key serializer is included in what's written for a keyed 
state backend in checkpoints. The namespace and state serializer already have 
their config snapshots included in the individual registered state's metainfo.

We should also include the configuration snapshot of the key serializer in 
{{KeyedBackendSerializationProxy}} so that we can also be flexible in allowing 
migration / transformation of the key in the future.

  was:
Currently, only the key serializer is included in what's written for a keyed 
state's metainfo in checkpoints. The namespace and state serializer already 
have their config snapshots included in the metainfo.

We should also include the configuration snapshot of the key serializer in 
there so that we can also be flexible in allowing migration / transformation of 
the key in the future.


> Add key serializer's config snapshot to KeyedBackendSerializationProxy
> ----------------------------------------------------------------------
>
>                 Key: FLINK-6600
>                 URL: https://issues.apache.org/jira/browse/FLINK-6600
>             Project: Flink
>          Issue Type: Improvement
>          Components: State Backends, Checkpointing
>            Reporter: Tzu-Li (Gordon) Tai
>            Assignee: Tzu-Li (Gordon) Tai
>             Fix For: 1.3.0, 1.4.0
>
>
> Currently, only the key serializer is included in what's written for a keyed 
> state backend in checkpoints. The namespace and state serializer already have 
> their config snapshots included in the individual registered state's metainfo.
> We should also include the configuration snapshot of the key serializer in 
> {{KeyedBackendSerializationProxy}} so that we can also be flexible in 
> allowing migration / transformation of the key in the future.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to