Community Articles

Find and share helpful community-sourced technical articles.
Labels (1)


I have a non kerberized cluster. I did apply however the jdbc intepreter is still not impersonated.

NOTE: From HDP 2.6.2 (Zeppelin 0.7.2) JDBC interpreter on non-kerberised cluster is impersonated by having the following property added into Zeppelin UI -> Interpreter -> JDBC config:


1. Go to Zeppelin UI -> Interpreter

The configuration for JDBC hive interpreter should look like

2. Edit JDBC interpreter

Remove properties hive.user and hive.password and save the changes. So, now the configuration looks like

3. Go to Zeppelin UI -> Credential

Add the credentials for the user like
Entity: jdbc.jdbc 
Username: <username> 
Password: <password>

4. Run the query

Go to your notebook and run the jdbc query for hive. In RM UI this query is now running by YOU

I followed the above process but i got the following error

Running on HDP,Zeppelin 0.7 with Kerberos disabled Connection refused (Connection refused) at Method) at at at at at at at org.apache.zeppelin.interpreter.remote.ClientFactory.create( at org.apache.zeppelin.interpreter.remote.ClientFactory.create( at org.apache.commons.pool2.BasePooledObjectFactory.makeObject( at org.apache.commons.pool2.impl.GenericObjectPool.create( at org.apache.commons.pool2.impl.GenericObjectPool.borrowObject( at org.apache.commons.pool2.impl.GenericObjectPool.borrowObject( at org.apache.zeppelin.interpreter.remote.RemoteInterpreterProcess.getClient( at org.apache.zeppelin.interpreter.remote.RemoteInterpreter.init( at org.apache.zeppelin.interpreter.remote.RemoteInterpreter.getFormType( at org.apache.zeppelin.interpreter.LazyOpenInterpreter.getFormType( at org.apache.zeppelin.notebook.Paragraph.jobRun( at at org.apache.zeppelin.scheduler.RemoteScheduler$ at java.util.concurrent.Executors$ at at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201( at java.util.concurrent.ScheduledThreadPoolExecutor$ at java.util.concurrent.ThreadPoolExecutor.runWorker( at java.util.concurrent.ThreadPoolExecutor$ at

@Vijay Kiran

Do not raise issues within the Article. Just create a separate HCC providing details of your JDBC interpreter as well as Credentials.

NOTE: The above was tested on HDP 2.6.1 only. And you are on if I am right.

Everyone following this article.

Make sure value is set for property zeppelin.jdbc.auth.type in jdbc interpreter either as SIMPLE or KERBEROS.

In my case, impersonation did not happen properly when the property has null value, and I changed the value to SIMPLE.

Take a Tour of the Community
Don't have an account?
Your experience may be limited. Sign in to explore more.
Version history
Last update:
‎08-17-2019 11:57 AM
Updated by:
Top Kudoed Authors