ASF GitHub Bot commented on FLINK-8451:

Github user twalthr commented on the issue:

    @tzulitai I think just writing out the arity is not enough. It really 
depends on the type of tuple. Maybe it would have been better to write out only 
the name of the class. But since we support tuple POJOs this might be a little 
bit risky. The tuple serializer serializes general subclasses for both Java and 
Scala and case classes.
    I tested case classes, tuples, `Either` and `Unit`. What do you think we 
should test as well? The other serializers do not include classes that need to 
be snapshotted.

> CaseClassSerializer is not backwards compatible in 1.4
> ------------------------------------------------------
>                 Key: FLINK-8451
>                 URL: https://issues.apache.org/jira/browse/FLINK-8451
>             Project: Flink
>          Issue Type: Bug
>          Components: Type Serialization System
>    Affects Versions: 1.4.0, 1.5.0
>            Reporter: Timo Walther
>            Assignee: Timo Walther
>            Priority: Blocker
>             Fix For: 1.5.0, 1.4.2
> There seems to be problems with the updated Scala version and the 
> CaseClassSerializer that make it impossible to restore from a Flink 1.3 
> savepoint.
> http://mail-archives.apache.org/mod_mbox/flink-user/201801.mbox/%3CCACk7FThV5itjSj_1fG9oaWS86z8WTKWs7abHvok6FnHzq9XT-A%40mail.gmail.com%3E
> http://mail-archives.apache.org/mod_mbox/flink-user/201801.mbox/%3C7CABB00B-D52F-4878-B04F-201415CEB658%40mediamath.com%3E

This message was sent by Atlassian JIRA

Reply via email to