Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1005
Merging it into master and branch-0.6
---
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 Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1005
@jongyoul Right, it's not dynamically configurable. Interpreter need to be
restarted to reconfigure.
I think it's possibly related to ZEPPELIN-999 and it's long term plan.
Let's say
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1005
@Leemoonsoo I've missed something. I've known it was not configurable
dynamically. Let me check.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1005
I was thinking just creating multiple interpreter settings if user want to
use different scheduler. Then just returning appropriate scheduler from
getScheduler() by configuration would be
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1005
Looks great, thank you for prompt update!
@jongyoul is there a reason to make it configurable from another PR instead
of this one? Just curious
---
If your project is set up for it, you
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1005
@Leemoonsoo I also agree to makes this configurable. I'll follow up this
with another PR. I also think we need to replace using getScheduler to another
way.
---
If your project is set up for
