Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/681#issuecomment-103075554
There are quite a few implicit assumptions in this pull request, some of
which have quite an impact:
- The `Client` is bound to a session now. Should we tie it strictly to a
session, meaning it has to be initialized with a `JobID`, or lazily pick up the
session. What happens if you submit a JobGraph that comes from a different
session? Does it track multiple sessions then?
- If the `Client` manages remote sessions, it should be created on the
first use of the remote executor, and then be kept.
- The `LocalExecutor` used in the `LocalExecutionEnvironment` should
probably allow you to maintain sessions as well. It would need to be started on
the first execution and stopped when the environment terminates the session or
runs out of scope.
- I think it makes a lot of sense to automatically terminate sessions as
soon as the environment or the executor runs out of scope (becomes finalizable
or garbage collectible).
---
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.
---
