Github user asfgit closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/844
---
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 fea
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/844#issuecomment-213170425
merging if no more comment
---
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 projec
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/844#issuecomment-212784586
Looks good to me
---
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
Github user FRosner commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/844#issuecomment-212769849
Thanks for your comment, @felixcheung. If the parent communicates the
signal properly, it is not going to be a problem.
I tested it and it seemed to
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/844#issuecomment-212638923
Would the interpreters be a problem for your case? Individual interpreter
processes are started by interpreter.sh
---
If your project is set up for it,
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/844#issuecomment-212115679
+ @Leemoonsoo
---
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 h
GitHub user FRosner opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/844
ZEPPELIN-815 don't create a sub shell for the runner
### What is this PR for?
This pull request is supposed to fix ZEPPELIN-815. The issue is that one
cannot stop Zeppelin by se
