GitHub user mfelgamal opened a pull request:

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

    Adding extra libraries to livy

    ### What is this PR for?
    Adding extra libraries to livy interpreter which isn't exist by default.
    
    ### What type of PR is it?
    [ Improvement ]
    
    ### Todos
    * [Test case ] - Task
    
    ### What is the Jira issue?
    *  [ZEPPELIN-1258]
    
    ### How should this be tested?
    - Create new livy interpreter or modify the default.
    - Set `livy.spark.driver.extraClassPath` and 
`livy.spark.executor.extraClassPath` to path of libraries.
    
    ### Screenshots (if appropriate)
    
![](https://s32.postimg.org/cxo94lzc5/livy_example_with_external_library.png)
    ![](https://s31.postimg.org/41gbe8hwr/add_Classpath_property_to_livy.png)
    
    ### Questions:
    * Does the licenses files need update? no
    * Is there breaking changes for older versions? no
    * Does this needs documentation? yes


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

    $ git pull https://github.com/novelari/incubator-zeppelin 
feature/modifying-livy-doc

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

    https://github.com/apache/zeppelin/pull/1255.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 #1255
    
----
commit 2586651ab9768e484e04a840978d6db8d5659f48
Author: Fouad <fuad.assay...@gmail.com>
Date:   2016-05-29T14:39:08Z

    Merge pull request #2 from apache/master
    
    update from original

commit 03a1e80f8f3115a75c42fa25fdaa06e7dd2cbc28
Author: mfelgamal <mahmoudf.elga...@gmail.com>
Date:   2016-07-19T18:28:46Z

    Merge pull request #4 from apache/master
    
    merge master

commit 98090abc075b97e3896ae6ea0c6e48f57e8d6434
Author: mahmoudelgamal <mahmoudf.elga...@gmail.com>
Date:   2016-07-19T22:12:54Z

    Adding external libraries to livy

----


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