[
https://issues.apache.org/jira/browse/FLINK-12870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Fedulov updated FLINK-12870:
--------------------------------------
Description:
There are certain pitfall when modifying classes used as keys.
For instance, removing a field from a key's class would cause nondeterministic
behavior when using RocksDB state backend, which relies on binary objects
identity, rather than hashCode implementation.
Documentation should mention that keys evolution is not supported and
specifically that when using Kryo serializers, framework would not be able to
capture potential incompatibility with the previous state format.
was:Add description of schema evolution limitations for keys
> Improve documentation of keys schema evolution
> ----------------------------------------------
>
> Key: FLINK-12870
> URL: https://issues.apache.org/jira/browse/FLINK-12870
> Project: Flink
> Issue Type: Improvement
> Components: Documentation
> Reporter: Alexander Fedulov
> Assignee: Alexander Fedulov
> Priority: Major
>
> There are certain pitfall when modifying classes used as keys.
> For instance, removing a field from a key's class would cause
> nondeterministic behavior when using RocksDB state backend, which relies on
> binary objects identity, rather than hashCode implementation.
> Documentation should mention that keys evolution is not supported and
> specifically that when using Kryo serializers, framework would not be able to
> capture potential incompatibility with the previous state format.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
