GitHub user zjffdu opened a pull request:

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

    ZEPPELIN-1473. It is not necessary to create SQLContext in LivyInterpreter

    ### What is this PR for?
    Livy will create SQLContext/HiveContext internally, (LIVY-94), so it is not 
necessary to create that in LivyInterpreter. Otherwise sqlContext in zeppelin 
will override that in livy. 
    
    
    
    ### What type of PR is it?
    [Bug Fix]
    
    ### Todos
    * [ ] - Task
    
    ### What is the Jira issue?
    * https://issues.apache.org/jira/browse/ZEPPELIN-1473
    
    ### How should this be tested?
    Tested manually.  HiveContext is created properly in livy, and can access 
hive data. 
    
    ### Screenshots (if appropriate)
    
![image](https://cloud.githubusercontent.com/assets/164491/18743886/bff7ae8e-80ed-11e6-83e6-0769c30e4094.png)
    
    ### Questions:
    * Does the licenses files need update? No
    * Is there breaking changes for older versions? No
    * Does this needs documentation? No
    
    …reter

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

    $ git pull https://github.com/zjffdu/zeppelin ZEPPELIN-1473

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

    https://github.com/apache/zeppelin/pull/1450.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 #1450
    
----
commit bae46a1f025855939e559bef8196157eb8317b25
Author: Jeff Zhang <zjf...@apache.org>
Date:   2016-09-22T09:53:51Z

    ZEPPELIN-1473. It is not necessary to create SQLContext in LivyInterpreter

----


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