[jira] [Created] (ZEPPELIN-5309) Notebooks lose their interpreter binding after upgrading to 0.9.0

["Daniel Gies (Jira)" <ji...@apache.org>]

Daniel Gies created ZEPPELIN-5309:
-------------------------------------

             Summary: Notebooks lose their interpreter binding after upgrading to 0.9.0
                 Key: ZEPPELIN-5309
                 URL: https://issues.apache.org/jira/browse/ZEPPELIN-5309
             Project: Zeppelin
          Issue Type: Bug
    Affects Versions: 0.9.0
            Reporter: Daniel Gies


When upgrading a Zeppelin 0.8.1 instance to 0.9.0, the interpreter bindings of notebooks are lost.  As a result, notebooks cannot run their paragraphs until the interpreter is manually rebound.  Manually rebinding the interpreter on each notebook is completely unworkable for large multi-tenant instances.

 

In an 0.8.1 instance with an interpreter named "gcp_presto", I created a note named "InterperterBinding" with a default interpreter "gcp_presto" and one paragraph containing "show schemas".  Then I upgraded the instance to 0.9.0 and ran bin/upgrade-note.sh

When I restarted Zeppelin and viewed the note, the interpreter binding had reverted to the value of zeppelin.interpreter.group.default (spark), and the paragraph will not run unless prefixed with %gcp_presto

 

Before the upgrade, interpreter.json contained this snippet:

"2G1YJDE62":["gcp_presto","spark","md","python2"]

After upgrade, interpreter.json removed the interpreterBinding section, and the note.zpln file has no defaultInterpreterGroup section.

 

The expected behavior is that the notebook's interpreter binding would be migrated from the interperterBinding section of /zeppelin/conf/interpreter.json into the defaultInterpreterGroup section of note.zpln

For Notebooks bound to multiple interpreters, we probably want to migrate only the first value to defaultInterpreterGroup



--
This message was sent by Atlassian Jira
(v8.3.4#803005)