Github user asfgit closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/557
---
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 Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/557#issuecomment-167616036
Tested and LGTM.
Merge if there're no more discussions
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user astroshim commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/557#issuecomment-167461320
@Leemoonsoo Thank you for making clear.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/557#issuecomment-167280810
@Leemoonsoo
I took a look at previous logs, and its behavior was somewhat strange.
I'll file an issue regarding strange behavior with logs. (Woul
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/557#issuecomment-167275152
@astroshim right, I think separated interpreter process for cron job or
similar would be a good approach for this issues. I know that there are places
wi
Github user astroshim commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/557#issuecomment-167243619
Hello. @felixcheung
You're right.. The interpreter process is shared now but I think
interpreter process will be separated as user option.
what d
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/557#issuecomment-167172536
@Leemoonsoo
It occurred while I was experimenting several things together so I'm not
100% sure that we can't handle interpreter via UI.
I'll try
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/557#issuecomment-167169459
I think interpreter restart should abort pending / running jobs.
If it raise `Scheduler already terminated` need to be fixed. @HeartSaVioR
do you mind
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/557#issuecomment-167163100
Actually I was trying to restart the interpreter first for each job run via
REST API, but gave up because it throws ```Scheduler already terminated``` whe
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/557#issuecomment-167152568
Would it be possible the interpreter restart happens in the middle of
another running notebook if more one are scheduled to around the same time?
Inte
10 matches
Mail list logo
