You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2021/06/06 10:53:02 UTC

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

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

Flink Jira Bot updated FLINK-19999:
-----------------------------------
      Labels: auto-deprioritized-major auto-unassigned  (was: auto-unassigned stale-major)
    Priority: Minor  (was: Major)

This issue was labeled "stale-major" 7 ago and has not received any updates so it is being deprioritized. If this ticket is actually Major, please raise the priority and ask a committer to assign you the issue or revive the public discussion.


> 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, 1.12.0
>            Reporter: Nico Kruber
>            Priority: Minor
>              Labels: auto-deprioritized-major, auto-unassigned
>
> 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)