Github user Leemoonsoo commented on the pull request:

    https://github.com/apache/incubator-zeppelin/pull/222#issuecomment-132361024
  
    Thanks for the contribution!
    
    At the moment, it can be done by user listing interpreters in 
`zeppelin.interpreters` with order.
    First seen in this list becomes default interpreter for the group.
    
    for example
    ```
    <property>
      <name>zeppelin.interpreters</name>
      
<value>org.apache.zeppelin.spark.SparkInterpreter,org.apache.zeppelin.spark.PySparkInterpreter</value>
    </property>
    ```
    makes `%spark` default, 
    
    ```
    <property>
      <name>zeppelin.interpreters</name>
      
<value>org.apache.zeppelin.spark.PySparkInterpreter,org.apache.zeppelin.spark.SparkInterpreter</value>
    </property>
    ```
    makes `%pyspark` default.
    
    it requires user edit configuration file and restart Zeppelin. and can not 
be applied to individual notebook differently. So i agree on having better way 
of choosing default interpreter. 
    
    This branch let user set default interpreter name in 'interpreter' menu as 
a property value. However, i think it's not very natural, because
     - Choosing default interpreter 'group' is being done in interpreter 
binding menu and Choosing default 'interpreter' is being done in interpreter 
property setting menu. not very consistent.
     - Choosing default interpreter 'group' applied per notebook. but choosing 
default 'interpreter' applied per interpreter setting. it is also confusing.
    
    My suggestion is let user drag and drop individual interpreters, in group, 
inside of interpreter binding menu.
    
    
![image](https://cloud.githubusercontent.com/assets/1540981/9343320/18f0323c-45b6-11e5-9789-d09e642e3c11.png)
    
    So user can set default interpreter 'group' and default 'interpreter' 
together in the same menu, and both applied per notebook. 
    
    What do you think?


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

Reply via email to