[GitHub] zeppelin issue #2561: ZEPPELIN-2893. Pass non spark.* of spark interpreter p...

Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/2561 @felixcheung Please help review --- 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 a

[GitHub] zeppelin pull request #2562: ZEPPELIN-2645. Adding way to register RemoteInt...

GitHub user zjffdu opened a pull request: https://github.com/apache/zeppelin/pull/2562 ZEPPELIN-2645. Adding way to register RemoteInterpreterServer's port into InterpreterProcess ### What is this PR for? Rebase PR #2418 , still use thrift as the communication protocol bet

[GitHub] zeppelin pull request #2561: ZEPPELIN-2893. Pass non spark.* of spark interp...

GitHub user zjffdu opened a pull request: https://github.com/apache/zeppelin/pull/2561 ZEPPELIN-2893. Pass non spark.* of spark interpreter properties to spark app driver ### What is this PR for? Straightforward change for allowing pass non spark.* properties to spark app drive

[GitHub] zeppelin pull request #2554: [ZEPPELIN-2627] Interpreter Component Refactori...

Github user asfgit closed the pull request at: https://github.com/apache/zeppelin/pull/2554 --- 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 e

[GitHub] zeppelin issue #2554: [ZEPPELIN-2627] Interpreter Component Refactoring

Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/2554 Thanks @Leemoonsoo for the review, I will merge it if no more comments. And will do the change in the following PR as there's still remaining work for the refactoring. --- If your project is set

[GitHub] zeppelin issue #2560: [ZEPPELIN-2876]. Integrate with Livy 0.4.0

Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/2560 Actually this livy interprete support both livy 0.2.0 / 0.3.0 /0.4.0, because livy's rest api doesn't change, only its java package name changes. So I can not add integration test for both of these

[GitHub] zeppelin issue #2554: [ZEPPELIN-2627] Interpreter Component Refactoring

Github user Leemoonsoo commented on the issue: https://github.com/apache/zeppelin/pull/2554 Thanks @zjffdu for great work. LGTM --- 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 featur

[GitHub] zeppelin issue #2560: [ZEPPELIN-2876]. Integrate with Livy 0.4.0

Github user prabhjyotsingh commented on the issue: https://github.com/apache/zeppelin/pull/2560 feasibility ask: Like we support python2, and python3 do you think it makes sense to have 2 different interpreters (at-least for now) one that supports Livy-0.2.0/0.3.0 and other as Livy-4?

[GitHub] zeppelin issue #2558: sc.setLocalProperty(...) should be more deterministic

Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/2558 What about `PySparkInterpreter` and `SparkRInterpreter` ? --- 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 ha

[GitHub] zeppelin pull request #2560: [ZEPPELIN-2876]. Integrate with Livy 0.4.0

GitHub user zjffdu opened a pull request: https://github.com/apache/zeppelin/pull/2560 [ZEPPELIN-2876]. Integrate with Livy 0.4.0 ### What is this PR for? This is to integrate livy 0.4.0 which is livy's first apache release. Since the package name is changed, I can not supp