Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/1514
Close this PR, as I am refactoring LivyInterpreter in ZEPPELIN-1607
---
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
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/1514
Great, one question LGTM otherwise
---
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
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/1514
I am planing to add such rest api for livy, but for now livy don't have
such api for checking version.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/1514
Got it. Is there a way to version check Livy, like how we do Spark? Perhaps
a PR on Livy to expose that?
Just thinking this could be fragile when moving to SparkSession and so on
Github user prabhjyotsingh commented on the issue:
https://github.com/apache/zeppelin/pull/1514
Sure, got it. 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 feature
enabled and
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/1514
If you start livy.sql first, you will hit this issue, because
userSessionMap is null.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user gss2002 commented on the issue:
https://github.com/apache/zeppelin/pull/1514
@prabhjyotsingh I have only seen this issue with livy.sql as it is the only
one that shares the HashMap between livy.spark and livy.sql. livy.sparkr and
livy.pyspark do not share session info. In
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/1514
I plan to do it after #1462, could you also take a look at #1462 ?
---
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
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/1514
looks good. is it possible to have a test for this?
---
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
