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

Tzu-Li (Gordon) Tai closed FLINK-11772.
---------------------------------------
    Resolution: Fixed

Merged.

1.8.0: a22069ff8e80678c4d7a33c3ad349f0a4499567c
1.9.0: 8b8dd8031819336200005e690ca66deaed5b1268

> InternalTimerServiceSerializationProxy should not be serializing timers' key 
> / namespace serializers anymore
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-11772
>                 URL: https://issues.apache.org/jira/browse/FLINK-11772
>             Project: Flink
>          Issue Type: Bug
>          Components: API / DataStream
>            Reporter: Tzu-Li (Gordon) Tai
>            Assignee: Tzu-Li (Gordon) Tai
>            Priority: Blocker
>              Labels: pull-request-available
>             Fix For: 1.8.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> All of the changes done to managed state surrounding how we no longer 
> Java-serialize serializers anymore and only write the serializer snapshot, as 
> well as how serialization compatibility checks should go through the new 
> {{TypeSerializerSnapshot}} / {{TypeSerializerSchemaCompatibility}} 
> interfaces, was not reflected to timers.
> This was mainly due to the fact that timers were not handled by state 
> backends (and were therefore not managed state) in the past, and were handled 
> in an isolated manner by the {{InternalTimerServiceSerializationProxy}}.
> The {{InternalTimerServiceSerializationProxy}} therefore needs to be updated 
> accordingly.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to