Github user bikassaha commented on the issue:
https://github.com/apache/zeppelin/pull/1557
Perhaps for this issue and other similar issues related to multiple users,
the mode for the livy interpreter should be scoped instead of shared. If we run
1 interpreter per user
Github user bikassaha commented on the issue:
https://github.com/apache/zeppelin/pull/1557
@zjffdu Isolated would also be valid but perhaps an overkill. So default of
scoped makes sense.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user bikassaha commented on the issue:
https://github.com/apache/zeppelin/pull/1787
In a different jira, should we consider removing this check for 2.1, 2.2
since its unlikely that Spark will break common APIs in dot releases. Perhaps
the policy can change to adding a check
Github user bikassaha commented on the issue:
https://github.com/apache/zeppelin/pull/2974
The description says "on hovering the (circle) you will see success / error
message for the respective interpreter." I wonder if that is going to show
whats wrong in starting/
Github user bikassaha commented on the issue:
https://github.com/apache/zeppelin/pull/2974
Lets say I restarted the interpreter. Between that time and the interpreter
actually starting, what icon is shown for the "start in progress state?" A
blinking green?
Github user bikassaha commented on the issue:
https://github.com/apache/zeppelin/pull/2974
I am guessing that would depend on whether we want to user to continue
doing other stuff or make them wait for the interpreter to start/restart.
The interpreter page is kind of a global
Github user bikassaha commented on the issue:
https://github.com/apache/zeppelin/pull/2974
Thats a good point. Though I thought interpreter restart was available from
the note itself. Is that not the case? Agree interpreter controls/settings
between admin/user needs to be looked
Github user bikassaha commented on the issue:
https://github.com/apache/zeppelin/pull/2974
Does "ready to run" mean code can be executed in the note?
---
Github user bikassaha commented on the issue:
https://github.com/apache/zeppelin/pull/3162
+1 lgtm
---
Github user bikassaha commented on the issue:
https://github.com/apache/zeppelin/pull/2818
zeppelin.livy.restart_dead_session - Is this an interpreter level setting?
Will it start only that users livy session?
---
Github user bikassaha commented on the issue:
https://github.com/apache/zeppelin/pull/2818
Can this be specified on a per notebook basis using the %conf interpreter?
It may be difficult to turn this on globally because of the various reasons why
sessions may die.
Would
11 matches
Mail list logo
