[jira] [Created] (FLINK-19999) State Processor API classes leaking into savepoint

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Created] (FLINK-19999) State Processor API classes leaking into savepoint

Shang Yuanchun (Jira)
Nico Kruber created FLINK-19999:
-----------------------------------

             Summary: State Processor API classes leaking into savepoint
                 Key: FLINK-19999
                 URL: https://issues.apache.org/jira/browse/FLINK-19999
             Project: Flink
          Issue Type: Bug
          Components: API / State Processor
    Affects Versions: 1.11.2
            Reporter: Nico Kruber


Currently, any configuration for serializers that you are using when writing a State Processor API job will be shared with the serializers that are used for writing a savepoint. However, your normal job shouldn't necessarily depend on (helper) classes that you only use in the StateProc API job.

By default, for example, {{ExecutionConfig#autoTypeRegistrationEnabled = true}} and thus classes like {{org.apache.flink.runtime.checkpoint.OperatorSubtaskState}} will be registered with Kryo and will thus also be needed when reading the created savepoint if you have Kryo serialization in your job.

This particular instance can be worked around by calling {{ExecutionConfig#disableAutoTypeRegistration()}} but the problem is probably bigger and extends to other type registrations, e.g. POJOs, as well.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)