GitHub user prabhjyotsingh opened a pull request:

    https://github.com/apache/zeppelin/pull/2088

    [ZEPPELIN-2203] In case of 'spark2' default interpreter, both '%spark' and 
'%spark2' point to Spark2.

    ### What is this PR for?
    In case of 'spark2' default interpreter, both '%spark' and '%spark2' point 
to Spark2.
    
    ### What type of PR is it?
    [Bug Fix]
    
    
    ### What is the Jira issue?
    * [ZEPPELIN-2203](https://issues.apache.org/jira/browse/ZEPPELIN-2203)
    
    
    ### How should this be tested?
    Create two interpreters with name spark(with spark 1.6) and spark2 (with 
spark 2.0). Now set default interpreter as spark2 for a notebook. Now execute 
"%spark sc.version" notice it prints spark2 version
    
    ### Screenshots (if appropriate)
    
    Before
    
![zeppelin-2203_before](https://cloud.githubusercontent.com/assets/674497/23493122/70b46446-ff2f-11e6-881d-39acc0727627.gif)
    
    
    After
    
![zeppelin-2203_after](https://cloud.githubusercontent.com/assets/674497/23493123/70b6f1ca-ff2f-11e6-8566-1da7f943ea56.gif)
    
    
    
    ### Questions:
    * Does the licenses files need update? N/A
    * Is there breaking changes for older versions? N/A
    * Does this needs documentation? N/A


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/prabhjyotsingh/zeppelin ZEPPELIN-2203

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/zeppelin/pull/2088.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2088
    
----
commit 0c3d04a7e223b68df8a3f398af5b65b965d4457d
Author: Prabhjyot Singh <prabhjyotsi...@gmail.com>
Date:   2017-03-02T04:16:15Z

    ZEPPELIN-2203: have a exact name check before returning settings

----


---
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