question Re: Trying to create phoenix interpreter using %jdbc in Zeppelin using 2.5 in Archives of Support Questions (Read Only)

Trying to create phoenix interpreter using %jdbc in Zeppelin using 2.5

gkeys — Sun, 18 Aug 2019 13:15:18 GMT

I am trying to create phoenix interpreter using %jdbc in Zeppelin using 2.5 and am not succeeding.

Steps are:

Log into Zeppelin (sandbox 2.5)
Create new interpreter as follows
restart (just to be paranoid)
go to my notebook and bind interpreter
when I run with %jdbc(phoenix) I get Prefix not found.
when I run it with %jdbc.phoenix I get jdbc.phoenix interpreter not found

What am I missing?

Re: Trying to create phoenix interpreter using %jdbc in Zeppelin using 2.5

rgelhausen — Tue, 13 Sep 2016 05:07:59 GMT

Hi, @gkeys, following the RedShift example here, the properties in your JDBC interpreter settings would be phoenix.user, phoenix.driver, phoenix.url, instead. Since you have modified the "default" prefix, does the plain "%jdbc" not work for the interpreter setting?

Re: Trying to create phoenix interpreter using %jdbc in Zeppelin using 2.5

TimothySpann — Tue, 13 Sep 2016 08:35:38 GMT

I just installed HDP 2.5 from Ambari on a small openstack cluster choosing Zeppelin from ambari.

%jdbc(phoenix)

select * from phillycrime limit 100

worked for me.

Try to restart the jdbc interpreter

Make sure you have:

under:

jdbc %jdbc (default)

edit restart remove

Option

shared Interpreter for note

Connect to existing process

phoenix.driver org.apache.phoenix.jdbc.PhoenixDriver

phoenix.hbase.client.retries.number 1

phoenix.password

phoenix.url jdbc:phoenix:192.168.1.100:/hbase-unsecure

phoenix.user phoenixuser

Re: Trying to create phoenix interpreter using %jdbc in Zeppelin using 2.5

gkeys — Tue, 13 Sep 2016 23:04:11 GMT

@Timothy Spann very effective answer, but similar information as @Randy Gelhausen and he was first in.

Re: Trying to create phoenix interpreter using %jdbc in Zeppelin using 2.5

gkeys — Tue, 13 Sep 2016 23:07:05 GMT

@Randy Gelhausen

Thanks. What threw me off is that when creating a new jdbc interpretter (at least in sandbox) it is prepopulutated with default prefix properties and psql values.. Did not know that entire property and value needed to be deleted and recreated with new prefix (vs only new values).