[jira] [Created] (AMBARI-22223) Account for hive security, transport mode and SSL in zeppelin's jdbc interpreter setting

[Kshitij Badani (JIRA)]

Kshitij Badani created AMBARI-3:
---

 Summary: Account for hive security, transport mode and SSL in 
zeppelin's jdbc interpreter setting
 Key: AMBARI-3
 URL: https://issues.apache.org/jira/browse/AMBARI-3
 Project: Ambari
  Issue Type: Bug
Affects Versions: 2.6.0
Reporter: Kshitij Badani
 Fix For: 2.6.0


In case of JDBC interpreter auto-configuration, URLs being set are not 
accounting for security, transport mode and SSL upon zeppelin server restart 
via ambari. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (AMBARI-20563) Zeppelin : livy2 interpreter is not getting created by default

[Kshitij Badani (JIRA)]

Kshitij Badani created AMBARI-20563:
---

 Summary: Zeppelin : livy2 interpreter is not getting created by 
default
 Key: AMBARI-20563
 URL: https://issues.apache.org/jira/browse/AMBARI-20563
 Project: Ambari
  Issue Type: Bug
  Components: blueprints
Affects Versions: 2.5.1
Reporter: Kshitij Badani
 Fix For: 2.5.1


Whenever Spark2 and Livy2 is installed on the cluster, I can see only Spark2 
interpreter getting created in Zeppelin and not the Livy2 interpreter.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (AMBARI-20397) Zeppelin: Spark2 and Livy2 interpreter config disappear during stack upgrade

[Kshitij Badani (JIRA)]

Kshitij Badani created AMBARI-20397:
---

 Summary: Zeppelin: Spark2 and Livy2 interpreter config disappear 
during stack upgrade
 Key: AMBARI-20397
 URL: https://issues.apache.org/jira/browse/AMBARI-20397
 Project: Ambari
  Issue Type: Bug
  Components: ambari-upgrade
Affects Versions: 2.5.0
Reporter: Kshitij Badani
 Fix For: 2.5.0


During stack upgrade spark2 and livy2 interpreters are not present in zeppelin 
by default. Typically for a fresh install- when spark2 service is detected , 
those 2 interpreters are by default created for user out-of-the box



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (AMBARI-20362) Enable Authentication in Zeppelin out of Box

[Kshitij Badani (JIRA)]

Kshitij Badani created AMBARI-20362:
---

 Summary: Enable Authentication in Zeppelin out of Box
 Key: AMBARI-20362
 URL: https://issues.apache.org/jira/browse/AMBARI-20362
 Project: Ambari
  Issue Type: Bug
  Components: blueprints
Affects Versions: 2.5.0
Reporter: Kshitij Badani
 Fix For: 2.5.0


Right now Zeppelin does not have any authentication enabled out of the box.
As the security sensitivity is ever increasing we should enable authentication 
by default.
We can use the same account Ambari Admin uses to authenticate with Zeppelin.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (AMBARI-20343) Zeppelin: Configure both Hive and Hive interactive interpreters whenever required

[Kshitij Badani (JIRA)]

Kshitij Badani created AMBARI-20343:
---

 Summary: Zeppelin: Configure both Hive and Hive interactive 
interpreters whenever required
 Key: AMBARI-20343
 URL: https://issues.apache.org/jira/browse/AMBARI-20343
 Project: Ambari
  Issue Type: Bug
  Components: blueprints
Affects Versions: 2.5.0
Reporter: Kshitij Badani
 Fix For: 2.5.0


Currently only jdbc(hive) is present in the interpreter config. But lets say if 
we have only HSI (hive server interactive) present on our cluster , or if we 
have both HSI and Hive present then we need some changes to the way 
interpreters are being defined

We should use %jdbc(hive) refer Hive interactive when only Hive interactive is 
present in the cluster.
Otherwise %jdbc(hive) for Hive and %jdbc(hive_interactive) for Hive interactive 
based on the availability of Hive/Hive interactive.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (AMBARI-17632) Issues observed with Zeppelin JDBC interpreter configurations

[Kshitij Badani (JIRA)]

Kshitij Badani created AMBARI-17632:
---

 Summary: Issues observed with Zeppelin JDBC interpreter 
configurations
 Key: AMBARI-17632
 URL: https://issues.apache.org/jira/browse/AMBARI-17632
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.4.0
Reporter: Kshitij Badani
 Fix For: 2.4.0


It is observed that the dependencies for phoenix are not configured in JDBC 
interpreter out-of-the-box. A user has to manually configure it 
(org.apache.phoenix:phoenix-core:4.4.0-HBase-1.0) and save the interpreter 
configurations.

After configuring dependency,  Zeppelin does not work with phoenix .

My Zeppelin JDBC interpreter configs corresponding to pheonix are

phoenix.driver  org.apache.phoenix.jdbc.PhoenixDriver
phoenix.hbase.client.retries.number 1
phoenix.password
phoenix.url jdbc:phoenix::2181:/hbase-unsecure
phoenix.userphoenixuser

When I try to run query:
%jdbc(phoenix)
create table if not exists PRICES (
 SYMBOL varchar(10),
 DATE   varchar(10),
 TIME varchar(10),
 OPEN varchar(10),
 HIGH varchar(10),
 LOWvarchar(10),
 CLOSE varchar(10),
 VOLUME varchar(30),
 CONSTRAINT pk PRIMARY KEY (SYMBOL, DATE, TIME)
) 

It gives PhoenixIOException
class org.apache.phoenix.exception.PhoenixIOException
org.apache.phoenix.util.ServerUtil.parseServerException(ServerUtil.java:108)
org.apache.phoenix.query.ConnectionQueryServicesImpl.ensureTableCreated(ConnectionQueryServicesImpl.java:879)
org.apache.phoenix.query.ConnectionQueryServicesImpl.createTable(ConnectionQueryServicesImpl.java:1213)
org.apache.phoenix.query.DelegateConnectionQueryServices.createTable(DelegateConnectionQueryServices.java:112)
org.apache.phoenix.schema.MetaDataClient.createTableInternal(MetaDataClient.java:1902)
org.apache.phoenix.schema.MetaDataClient.createTable(MetaDataClient.java:744)
org.apache.phoenix.compile.CreateTableCompiler$2.execute(CreateTableCompiler.java:186)
org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:303)
org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:295)
org.apache.phoenix.call.CallRunner.run(CallRunner.java:53)
org.apache.phoenix.jdbc.PhoenixStatement.executeMutation(PhoenixStatement.java:293)
org.apache.phoenix.jdbc.PhoenixStatement.executeUpdate(PhoenixStatement.java:1236)
org.apache.phoenix.query.ConnectionQueryServicesImpl$12.call(ConnectionQueryServicesImpl.java:1891)
org.apache.phoenix.query.ConnectionQueryServicesImpl$12.call(ConnectionQueryServicesImpl.java:1860)
org.apache.phoenix.util.PhoenixContextExecutor.call(PhoenixContextExecutor.java:77)
org.apache.phoenix.query.ConnectionQueryServicesImpl.init(ConnectionQueryServicesImpl.java:1860)
org.apache.phoenix.jdbc.PhoenixDriver.getConnectionQueryServices(PhoenixDriver.java:162)
org.apache.phoenix.jdbc.PhoenixEmbeddedDriver.connect(PhoenixEmbeddedDriver.java:131)
org.apache.phoenix.jdbc.PhoenixDriver.connect(PhoenixDriver.java:133)
java.sql.DriverManager.getConnection(DriverManager.java:571)
java.sql.DriverManager.getConnection(DriverManager.java:187)
org.apache.zeppelin.jdbc.JDBCInterpreter.getConnection(JDBCInterpreter.java:222)
org.apache.zeppelin.jdbc.JDBCInterpreter.getStatement(JDBCInterpreter.java:233)
org.apache.zeppelin.jdbc.JDBCInterpreter.executeSql(JDBCInterpreter.java:292)
org.apache.zeppelin.jdbc.JDBCInterpreter.interpret(JDBCInterpreter.java:396)
org.apache.zeppelin.interpreter.LazyOpenInterpreter.interpret(LazyOpenInterpreter.java:94)
org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer$InterpretJob.jobRun(RemoteInterpreterServer.java:341)
org.apache.zeppelin.scheduler.Job.run(Job.java:176)
org.apache.zeppelin.scheduler.ParallelScheduler$JobRunner.run(ParallelScheduler.java:162)
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
java.util.concurrent.FutureTask.run(FutureTask.java:262)
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
java.lang.Thread.run(Thread.java:745) 




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)