Member since
07-13-2016
7
Posts
0
Kudos Received
0
Solutions
07-27-2016
01:46 PM
(Back from vacation.) Installed Zeppelin 0.6.0 from source in a CentOS VM, and it does see my custom interpreter! Thanks.
... View more
07-15-2016
01:06 PM
Thank you for the installation details. I'm currently setting up a new VM on which I'll perform a manual install of Zeppelin; I'll post the results here.
... View more
07-13-2016
03:53 PM
Thanks for your reply. Yes, I tried the static registration method as follows (in the DummyInterpreter class): static {
Interpreter.register("dummy", "dummy", DummyInterpreter.class.getName(),
new InterpreterPropertyBuilder()
.add("dummy.boolProp", "true", "Boolean property")
.add("dummy.intProp", "0", "Integer property")
.build()
);
}
I also tried building my interpreter against version 0.5.0-incubating (with the above static registration) but there was no difference whatsoever: Zeppelin wouldn't load the interpreter. I guess I'll have to do what I wanted to avoid: install Zeppelin "manually" on an HDP 2.4... ?
... View more
07-13-2016
01:46 PM
Hello, Context:
HDP Sandbox 2.4 Zeppelin 0.6.0 (pre-installed) -- zeppelin-server-0.6.0.2.4.0.0-169.jar specifically, although the Ambari UI reports version 0.0.5 (!).
I'm writing a custom interpreter for Zeppelin called "dummy" (does nothing interesting at the moment, hence the name). My com.dummy.DummyInterpreter class extends
org.apache.zeppelin.interpreter.Interpreter, as it should. I've built it against package org.apache.zeppelin:zeppelin-interpreter:0.6.0 and installed its jar in directory interpreter/dummy. The interpreter jar does contain a file called interpreter-setting.json at its "root" with the following contents: [
{
"group": "dummy",
"name": "dummy",
"className": "com.dummy.DummyInterpreter",
"properties": {
"boolProp": {
"envName": null,
"propertyName": "dummy.boolProp",
"defaultValue": "true",
"description": "Boolean property"
},
"intProp": {
"envName": null,
"propertyName": "dummy.intProp",
"defaultValue": "0",
"description": "Integer property"
}
}
}
]
I also added "com.dummy.DummyInterpreter" to setting "zeppelin.interpreters" in zeppelin-site.xml. However, I can't get Zeppelin to load it: Zeppelin does pick the "dummy" folder when restarted but it doesn't find the interpreter class, as evidenced by the following log excerpt: INFO - Reading /usr/hdp/current/zeppelin-server/lib/interpreter/ignite
INFO - Interpreter ignite.ignite found. class=org.apache.zeppelin.ignite.IgniteInterpreter
INFO - Interpreter ignite.ignitesql found. class=org.apache.zeppelin.ignite.IgniteSqlInterpreter
INFO - Reading /usr/hdp/current/zeppelin-server/lib/interpreter/dummy
INFO - Reading /usr/hdp/current/zeppelin-server/lib/interpreter/md
INFO - Interpreter md.md found. class=org.apache.zeppelin.markdown.Markdown
Unfortunately, there's no error reported... And strangely enough, this output looks more like what Zeppelin 0.5.0 would print than 0.6.0 would, based on my reading the source of Zeppelin's InterpreterFactory... What am I missing? Any help would be greatly appreciated.
... View more
Labels:
- Labels:
-
Apache Zeppelin
07-13-2016
11:42 AM
Just to be sure, I created a new VM instance of HDP 2.4 Sandbox and the version of Zeppelin notebook reported by Ambari is indeed wrong: 0.0.5 instead of 0.6.0.
... View more
07-13-2016
09:36 AM
I installed 2.4 Sandbox. Checking the Zeppelin server jar as you suggested (zeppelin-server-0.6.0.2.4.0.0-169.jar in my case) , it seems I do have Zeppelin 0.6.0. I don't remember performing any additional installation, so I don't know where the 0.0.5 comes from... So I built my interpreter using the proper version of Zeppelin. Now on to finding out why it doesn't load... Thank you for your reply.
... View more
07-13-2016
08:23 AM
Hello, HDP 2.4 Ambari's "Stack and version" reports the (pre-installed) Zeppelin notebook as being version 0.0.5, surely this is a mistake. According to the release notes [1] the version is 0.6.0. Is that right? Or is it 0.5.0 (and the version reported is a typo) ? (I'm trying to write a custom interpreter but it isn't loaded and there's no reason for that in Zeppelin's logs so I'm starting to wonder if I built my interpreter against the wrong version of Zeppelin, hence my looking at the version reported by Ambari...) [1] http://fr.hortonworks.com/wp-content/uploads/2016/03/ReleaseNotes_3_23_2016.pdf
... View more
Labels:
- Labels:
-
Apache Zeppelin