Well it doesn't. I think when we find thst we have a id for an interpreter that does not exist we should first tty to bind as if it was the first time we run the paragraph and only if we don't have any interpreter matching the %xx then show the error.
בתאריך יום ב׳, 17 באוג׳ 2015, 18:40 מאת Joel Zambrano <[email protected]>: > Oh I completely agree! I thought that when this happened the ui would ask > you to re bind the notebook to an interpreter. > > Thanks, > Joel > > > On Aug 17, 2015, at 8:08 AM, IT CTO <[email protected]> wrote: > > > > Thanks for the explanation BUT this looks like a bug and not a feature. > It > > would be hard to explain to user that they need to copy paste all the > > content of notebooks, right? > > > > בתאריך יום ב׳, 17 באוג׳ 2015, 17:57 מאת Joel Zambrano <[email protected] > >: > > > >> This is because interpreters and notebooks have unique ids and each > >> notebook is bound to one interpreter by ids. So even though the new > >> interpreter has the same name its is different and the notebook binding > >> refers to the old id. > >> > >> Thanks, > >> Joel > >> > >>> On Aug 17, 2015, at 1:09 AM, IT CTO <[email protected]> wrote: > >>> > >>> Hi, > >>> > >>> This is one of the problem that you don't know what is happening : > >>> > >>> 1) open a notebook and try %md ### this is a test > >>> 2) Run it and get the expected results > >>> 3) remove the interpreter using the interpreter settings page > >>> 4) try running the paragraph again and get an error : "md interpreter > not > >>> found" > >>> Log file will show: > >>> ERROR [2015-08-17 11:02:22,782] ({qtp2095490653-45} > >>> NotebookServer.java[runParagraph]:611) - Exception from run > >>> org.apache.zeppelin.interpreter.InterpreterException: md interpreter > not > >>> found > >>> at > >> > org.apache.zeppelin.notebook.NoteInterpreterLoader.get(NoteInterpreterLoader.java:148) > >>> at org.apache.zeppelin.notebook.Note.run(Note.java:267) > >>> at > >> > org.apache.zeppelin.socket.NotebookServer.runParagraph(NotebookServer.java:609) > >>> at > >> > org.apache.zeppelin.socket.NotebookServer.onMessage(NotebookServer.java:132) > >>> at > >> > org.apache.zeppelin.socket.NotebookSocket.onMessage(NotebookSocket.java:56) > >>> at > >> > org.eclipse.jetty.websocket.WebSocketConnectionRFC6455$WSFrameHandler.onFrame(WebSocketConnectionRFC6455.java:835) > >>> at > >> > org.eclipse.jetty.websocket.WebSocketParserRFC6455.parseNext(WebSocketParserRFC6455.java:349) > >>> at > >> > org.eclipse.jetty.websocket.WebSocketConnectionRFC6455.handle(WebSocketConnectionRFC6455.java:225) > >>> at > >> > org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:667) > >>> at > >> > org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52) > >>> at > >> > org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608) > >>> at > >> > org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543) > >>> at java.lang.Thread.run(Thread.java:745) > >>> > >>> 5) Add the interpreter back using the interpreter setting page > >>> 6) try running the paragraph again > >>> *still getting the same error both on page and in log* > >>> 7) open a new notebook and try using md > >>> 8) *everything works fine in the new notebook* > >>> > >>> So for some reason, after removing an interpreter and getting an error > it > >>> can't be re-attached to the notebook. > >>> BTW, even restarting the server did not sole the problem > >>> Eran > >> >
