[
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 pull-request-available
stale-minor (was: Avro AvroSchema auto-deprioritized-major
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
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: Minor
> Labels: Avro, AvroSchema, auto-deprioritized-major,
> pull-request-available, stale-minor
>
> 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)
