You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/02/27 13:12:00 UTC

[jira] [Updated] (FLINK-11772) InternalTimerServiceSerializationProxy should not be serializing timers' key / namespace serializers anymore

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

ASF GitHub Bot updated FLINK-11772:
-----------------------------------
    Labels: pull-request-available  (was: )

> 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: DataStream API
>            Reporter: Tzu-Li (Gordon) Tai
>            Assignee: Tzu-Li (Gordon) Tai
>            Priority: Blocker
>              Labels: pull-request-available
>             Fix For: 1.8.0
>
>
> 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)