Github user tillrohrmann commented on the pull request:
https://github.com/apache/flink/pull/1913#issuecomment-216816200
What happens if the Akka communication is local? Would that mean that the
list of registered Kryo types is shared between the `JobManager` and the
`Client`? This could lead to a problem if the list of registered types is
altered after submitting the first job (in detached mode). Maybe we have to
create a copy of the `ExecutionConfig`.
I think we should add some tests which verify the behaviour of
`SerializableCacheableValue`. Furthermore, we should add a test case for the
original problem.
Apart from that, the changes look good and +1 for merging.
---
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.
---