Github user sachingoel0101 commented on the pull request:
https://github.com/apache/flink/pull/1088#issuecomment-137421268
Sure.
---
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
Github user sachingoel0101 closed the pull request at:
https://github.com/apache/flink/pull/1088
---
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
Github user uce commented on the pull request:
https://github.com/apache/flink/pull/1088#issuecomment-137421164
I would move the discussion to the respective PR. Sachin, could you close
this PR?
---
If your project is set up for it, you can reply to this email and have your
reply app
Github user sachingoel0101 commented on the pull request:
https://github.com/apache/flink/pull/1088#issuecomment-137420928
Aha. I just had a brief look at the PR.
I had initially thought of implementing a start and stop method in the
`ExecutionEnvironment` but decided against it,
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-
GitHub user sachingoel0101 opened a pull request:
https://github.com/apache/flink/pull/1088
[FLINK-2615]Preserve executors for the entire run of program.
1. Prevents re-starts of local cluster several times on multiple executions.
2. Preserves the executor states for the entire r
