Regarding documentation, Spark interpreter expose ZeppelinContext [1] to use with variable 'z'. There can be some undocumented function and you check from the source code [2].
Also SparkInterpreter allows access InterpreterContext [3] from z.InterpreterContext() and this gives some low level access to some informations/objects that Zeppelin provides to interpreter. I have no brilliant idea where and how to document this, but if anyone interested, please feel free to update documentation [4]. Thanks, moon [1] http://zeppelin.apache.org/docs/0.7.0/interpreter/spark.html#zeppelincontext [2] https://github.com/apache/zeppelin/blob/v0.7.0/spark/src/main/java/org/apache/zeppelin/spark/ZeppelinContext.java [3] https://github.com/apache/zeppelin/blob/v0.7.0/zeppelin-interpreter/src/main/java/org/apache/zeppelin/interpreter/InterpreterContext.java [4] https://github.com/apache/zeppelin/tree/master/docs On Wed, Feb 15, 2017 at 6:31 AM Kir Iceman <kea...@gmail.com> wrote: > I'd be nice if it was possible to dynamically turn on and off REPL, so for > example on dev stage i'd leave it on and in prod i'll turn it off and turn > on only in case of some issue for debug purposes > > > > -- > View this message in context: > http://apache-zeppelin-users-incubating-mailing-list.75479.x6.nabble.com/After-upgrading-to-0-7-0-behaviour-changed-for-REPL-tp5070p5079.html > Sent from the Apache Zeppelin Users (incubating) mailing list mailing list > archive at Nabble.com. >
