Github user tillrohrmann commented on the pull request:
https://github.com/apache/flink/pull/1818#issuecomment-199363606
Due to the tight coupling of the ExecutionConfig and multiple Flink
components
(e.g. PojoSerializer) the automatic serialization and manual
deserialization of
user code objects via the UserCodeValue class caused problems. In order to
minimize
the impact of the changes, I changed the serialization strategy to an
explicit one.
One has to call `ExecutionConfig.serializeUserCode` to store the user code
objects in a SerializedValue
object and nulling the corresponding member fields. If that is not done,
then it is
assumed that the object is deserialized using a user code class loader. On
the receiving side one has to call `ExecutionConfig.deserializeConfig`
providing a class loader which knows the user code classes.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
