GitHub user zjffdu reopened a pull request:

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

    ZEPPELIN-1342. Adding dependencies via SPARK_SUBMIT_OPTIONS doesn't work on 
Spark 2.0.0

    ### What is this PR for?
    
    The root cause is due to the change of repl of scala-2.11. User needs to 
specify the jars in the repl setting explicitly.
    
    ### What type of PR is it?
    [Bug Fix]
    
    ### Todos
    * [ ] - Task
    
    ### What is the Jira issue?
    * https://issues.apache.org/jira/browse/ZEPPELIN-1342
    
    ### How should this be tested?
    Tested manually as shown in the screenshot. 
    
    ### Screenshots (if appropriate)
    
    
![image](https://cloud.githubusercontent.com/assets/164491/17997416/f26c262c-6ba0-11e6-8586-22a6a633b21b.png)
    
    ### Questions:
    * Does the licenses files need update? No
    * Is there breaking changes for older versions? No
    * Does this needs documentation? No
    


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

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

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

    https://github.com/apache/zeppelin/pull/1366.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 #1366
    
----
commit 56925d61e937fd8b14590a011c1139d3a1b27e4a
Author: Jeff Zhang <zjf...@apache.org>
Date:   2016-08-26T07:19:51Z

    ZEPPELIN-1342. Adding dependencies via SPARK_SUBMIT_OPTIONS doesn't work on 
Spark 2.0.0

commit 10f64e6264e9533209ab7d8b890945848672870a
Author: Jeff Zhang <zjf...@apache.org>
Date:   2016-08-27T02:34:50Z

    fix test failure

----


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