Github user zjffdu commented on the issue:
    @minahlee @prabhjyotsingh Please ignore my last comment. I just found that 
the issue of ZEPPELIN-1458 doesn't exist in branch-0.6.  But found another 
issue, @jongyoul It seems creating new interpreter breaks in branch-0.6. I 
created a new interpreter called spark2, but will hit the following error.
    It looks like in branch-0.6, we still load interpreter from 
Interpreter.registeredInterpreters rather than InterpereterSetting. 
    Interpreter.RegisteredInterpreter registeredInterpreter = 
              .get(group + "." + name);
          if (registeredInterpreter == null
              || registeredInterpreter.getClassName() == null) {
            throw new InterpreterException(replName + " interpreter not found");

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 or file a JIRA ticket
with INFRA.

Reply via email to