Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/1088#issuecomment-137418968
The current behavior is actually desired. You can explicitly start the
local executor, and explicitly stop it. When you did not explicitly start it,
you get an auto-shut down executor. This is quite flexible, no?
The LocalExecutionEnvironment is a local one-time environment. There is
code to extend it to sessions, which is really what we want to "keep context
and data around".
For that, there is part of the work here:
https://github.com/apache/flink/pull/858
It follows a very principled approach, where the responsibility of deciding
clearing / disposal of cached context and data is bound to a session. Sessions
have timeouts and scope reapers, and are managed by the execution environments,
not the executors.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
