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

Posted to dev@flink.apache.org by "Chesnay Schepler (Jira)" <ji...@apache.org> on 2022/08/17 16:27:00 UTC

[jira] [Created] (FLINK-29016) Clarify Kryo limitations w.r.t. schema evolution

Chesnay Schepler created FLINK-29016:
----------------------------------------

             Summary: Clarify Kryo limitations w.r.t. schema evolution
                 Key: FLINK-29016
                 URL: https://issues.apache.org/jira/browse/FLINK-29016
             Project: Flink
          Issue Type: Improvement
          Components: API / Type Serialization System
            Reporter: Chesnay Schepler
            Assignee: Chesnay Schepler
             Fix For: 1.16.0


While the schema evolution docs do state that Kryo isn't supported for schema evolution they don't really convey the gravity of the situation.
They should clarify that if Kryo is used for anything, even some data-structure containing POJOs (like an ArrayList, scala option/collection), that schema evolution will not be possible.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)