[
https://issues.apache.org/jira/browse/FLINK-23953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-23953:
-----------------------------------
Labels: Avro AvroSchema auto-deprioritized-major auto-deprioritized-minor
pull-request-available (was: Avro AvroSchema auto-deprioritized-major
pull-request-available stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> AvroSerializerSnapshot causes state migration even though the old and the new
> schemas are compatible
> ----------------------------------------------------------------------------------------------------
>
> Key: FLINK-23953
> URL: https://issues.apache.org/jira/browse/FLINK-23953
> Project: Flink
> Issue Type: Bug
> Components: API / Type Serialization System
> Affects Versions: 1.13.2
> Reporter: Iaroslav Zeigerman
> Priority: Not a Priority
> Labels: Avro, AvroSchema, auto-deprioritized-major,
> auto-deprioritized-minor, pull-request-available
>
> The problematic code is located
> [here|https://github.com/apache/flink/blob/release-1.13.2/flink-formats/flink-avro/src/main/java/org/apache/flink/formats/avro/typeutils/AvroSerializerSnapshot.java#L194].
> Returning COMPATIBLE_AFTER_MIGRATION seems completely unnecessary and causes
> issues during schema evolution. The COMPATIBLE_AS_IS status should be
> returned instead. Even the comment right above the shared snippet suggests
> that:
> {noformat}
> // The new serializer would be able to read data
> persisted with *this*
> // serializer, therefore no migration
> // is required.
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
