Thanks a ton Stefan, that was really helpful.
--
View this message in context:
http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Evolving-serializers-and-impact-on-flink-managed-states-tp14777p14837.html
Sent from the Apache Flink User Mailing List archive. mailing list arch
Hi,
yes, the assumption is correct. This is no instability, but actually stopping
the user to corrupt data through attempting an unsupported operation. Migration
required is the outcome of the compatibility check that would start a migration
process. For Avro, the serializer does not have to si
Hi Stefan,
Thanks a lot for such a helpful response. That really made thing a lot
clearer for me. Although at this point I have one more and probably last
question.
According to the Flink documentation,
[Attention] Currently, as of Flink 1.3, if the result of the compatibility
check acknowledge
Hi,
> 1. The article in question probably makes use of Flink serialization, what
> if I use Avro serde for the serialization and deserialization part. If I
> create a savepoint of my job, stop my flink, load the new POJO and continue
> from the savepoint, would avro's schema evolution feature perf
