You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@zeppelin.apache.org by "Darshan Mehta (JIRA)" <ji...@apache.org> on 2017/04/03 11:41:41 UTC

[jira] [Created] (ZEPPELIN-2343) Zeppeling interpreter dependencies are not copied when cloning EMR cluster

Darshan Mehta created ZEPPELIN-2343:
---------------------------------------

             Summary: Zeppeling interpreter dependencies are not copied when cloning EMR cluster
                 Key: ZEPPELIN-2343
                 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2343
             Project: Zeppelin
          Issue Type: Bug
            Reporter: Darshan Mehta


If interpreter.json file gets modified in EMR cluster, we can see the changes getting reflected after restarting zeppelin. However, if a cluster is cloned, the new interpreter.json does not have those changes.

Steps to reproduce:

- Create a cluster
- Modify interpreter.json and add a dependency (e.g. spark dep)
- Zeppelin notebooks will be able to use that dependency
- Now clone the cluster and check interpreter.json of new cluster
- Newly added dependency will not be there



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)