Re: Writing a remote interpreter in 0.9

Bidirectional callbacks instead of less effective callback/pooling? And if the interpreter registers, there is no need for add interpreter/remote application/remote port number? So this part of UI is obsolete in 0.9? If there is a local Zeppelin instance, the following in another process

Re: Writing a remote interpreter in 0.9

callback host is the Zeppelin Server host, RemoteInterpreterServer needs to know where is the Zeppelin Server and register to it, in that way they can establish bi-directional communication between Zeppelin Server and RemoteInterpreterServer. Artur Rataj 于2019年11月5日周二 下午6:08写道： > What is this ca

Re: Writing a remote interpreter in 0.9

What is this callback host in RemoteInterpreterServer? Does it specify a concrete instance of Zeppelin? If yes, why? I would think that the interpreter waits on a port and creates its new instances for any Zeppelin instance that connects. On Tue, Nov 5, 2019 at 8:58 AM Artur Rataj wrote: > > So I

Re: Writing a remote interpreter in 0.9

So I will write a local interpreter for now. I want to use Zeppelin as an UI of an app, but I do not want to put an app into Zeppelin sources, a remote interpreter would be very handy here. On Tue, Nov 5, 2019 at 2:30 AM Jeff Zhang wrote: > I think connecting to remote interpreter is broken i

Re: Writing a remote interpreter in 0.9

I think connecting to remote interpreter is broken in 0.9, because we introduce bi-directional communication channel in 0.9. https://issues.apache.org/jira/browse/ZEPPELIN-2035 Artur Rataj 于2019年11月5日周二 上午12:42写道： > Please, give me some hints... > > On Mon, Nov 4, 2019 at 5:39 PM Artur Rataj

Re: Writing a remote interpreter in 0.9

Please, give me some hints... On Mon, Nov 4, 2019 at 5:39 PM Artur Rataj wrote: > > To sum this up, > https://zeppelin.apache.org/docs/0.7.0/manual/interpreters.html#connecting-to-the-existing-remote-interpreter > says > > RemoteInterpreterServer interpreter=new RemoteInterpreterServer(3678); > /

Re: Writing a remote interpreter in 0.9

To sum this up, https://zeppelin.apache.org/docs/0.7.0/manual/interpreters.html#connecting-to-the-existing-remote-interpreter says RemoteInterpreterServer interpreter=new RemoteInterpreterServer(3678); // Here, 3678 is the port on which interpreter will listen. This constructor, however, does not

Re: Writing a remote interpreter in 0.9

So I attempted to write a rudimentary remote interpreter anyway, despite that isTest needs to be true for the remote server constructor to work. The effect is, the server's method createInterpreter throws NullPointerException, as it calls intpEventClient, which in turn is initialised only if isTest

Re: Writing a remote interpreter in 0.9

Yes, I can do that, but I would want to connect to my interpreter via any Zeppelin instance, not only via one customised, with an additional interpreter added to its sources at compile time. This is why I wanted to use a remote interpreter, i.e. one in an independent application. This constructor:

Re: Writing a remote interpreter in 0.9

The most simplest interpreter might be shell interpreter. You can create a simple interpreter module like sh module, and extend abstract class Interpreter. Refer http://zeppelin.apache.org/docs/0.8.2/development/writing_zeppelin_interpreter.html#make-your-own-interpreter https://github.com/apache

Re: Writing a remote interpreter in 0.9

I would need any way of writing a remote interpreter for Zeppelin 0.9. It would be useful to have some docs, an example or whatever which describes RemoteInterpreterServer in 0.9. No API docs in the sources, searching in turn for an actual usage of RemoteInterpreterServer on the web shows some no-m

Re: Writing a remote interpreter in 0.9

Usually you don't need to care about connection establish between RemoteInterpreterServer and Zeppelin-Server, these stuff are handled by zeppelin itself. Could you be more specific about what kind of issue you hit ? Artur Rataj 于2019年11月4日周一 下午10:10写道： > I used RemoteInterpreterServer without i

Re: Writing a remote interpreter in 0.9

I used RemoteInterpreterServer without intpEvenServerHost, connected via "connect to existing process" in Zeppelin and it produced: java.lang.RuntimeException: org.apache.thrift.TApplicationException: Internal error processing createInterpreter If intpEvenServerHost is "localhost", it causes imme

Writing a remote interpreter in 0.9

Hi, I want to write a remote interpreter for Zeppelin, but the API changed since https://zeppelin.apache.org/docs/0.7.0/manual/interpreters.html#connecting-to-the-existing-remote-interpreter was written. What is the difference between RemoteInterpreterServer with and without intpEvenServerHost? I