GitHub user mfelgamal opened a pull request: https://github.com/apache/incubator-zeppelin/pull/903
[ZEPPELIN-773] Adding support for spark interpreter to work with yarn⦠### What is this PR for? Adding support for zeppelin to run in yarn-cluster mode through Livy - Creating new interpreter (livy-spark) with (spark, pyspark, sparkr) - Extending the interpreter to allow manipulation in the configurations of Spark from zeppelin web ui. ### What type of PR is it? Feature ### Todos * [Test case ] - Task * [Documentation ] - Task ### What is the Jira issue? * [ZEPPELIN-773] ### How should this be tested? - Install Livy on https://github.com/cloudera/hue/tree/master/apps/spark/java - Start the Livy server - Start the Zeppelin and go to interpreter page, create livy interpreter with supported configurations - Run livy-interpreter on any of three modes (`%livy.spark` to spark, `%livy.pyspark` to python, `%livy.sparkr` to R) ***If you run on a cluster, the cluster should support yarn, and run livy-server in yarn mode*** ### Screenshots (if appropriate)   ### 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/livy-spark-interpreter Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-zeppelin/pull/903.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 #903 ---- commit 5492d3ce9eec9ec127a30c1a8432a8fc2d8e4910 Author: Mahmoud Elgamal <mahmoudf.elga...@gmail.com> Date: 2016-03-06T17:38:30Z [ZEPPELIN-773] Adding support for spark interpreter to work with yarn cluster mode through livy server ---- --- 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. ---