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/08 10:46:01 UTC
[jira] [Updated] (FLINK-12045) Support force migration between
incompatible state schemas/serializers
[ https://issues.apache.org/jira/browse/FLINK-12045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Flink Jira Bot updated FLINK-12045:
-----------------------------------
Labels: auto-unassigned pull-request-available stale-major (was: auto-unassigned pull-request-available)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Major but is unassigned and neither itself nor its Sub-Tasks have been updated for 30 days. I have gone ahead and added a "stale-major" to the issue". If this ticket is a Major, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.
> Support force migration between incompatible state schemas/serializers
> ----------------------------------------------------------------------
>
> Key: FLINK-12045
> URL: https://issues.apache.org/jira/browse/FLINK-12045
> Project: Flink
> Issue Type: Improvement
> Components: API / Type Serialization System, Runtime / State Backends
> Reporter: Yu Li
> Priority: Major
> Labels: auto-unassigned, pull-request-available, stale-major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Under certain circumstances user would choose to do force state schema migration, for example since we suggest to avoid using Kryo for state serialization, user might want to use POJO/Avro serializers instead and wish Flink automatically perform a force migration when required to.
> This JIRA targets at supporting such force migration requirements.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)