[
https://issues.apache.org/jira/browse/HIVE-22134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16916149#comment-16916149
]
Naveen Gangam commented on HIVE-22134:
--------------------------------------
Ran test
{code}
#!/bin/sh
export JAVA_HOME=/usr/java/jdk1.8.0_141-cloudera
export PATH=$PATH:$JAVA_HOME/bin
CLASSPATH=$CLASSPATH:$JAVA_HOME/jre/lib/rt.jar:/root/hive_jdbc_client.jar
CLASSPATH=$CLASSPATH:/root/hive-jdbc-3.1.2000.7.0.0.0-SNAPSHOT-standalone.jar
echo $CLASSPATH
java -cp ${CLASSPATH}
-Dkeytab.principal="hive/**********.cloudera.com@*.CLOUDERA.COM"
-Dkeytab.file=/var/run/cloudera-scm-agent/process/90-hive_on_tez-HIVESERVER2/hive.keytab
hive.test.HiveJDBCClient
"jdbc:hive2://******cloudera.com:10000/default;ssl=true;sslTrustStore=/etc/cdep-ssl-conf/CA_STANDARD/keystore.jks;sslTrustPassword=*****;principal=hive/****.cloudera.com@********.CLOUDERA.COM"
{code}
Output is
{code}
:/usr/java/jdk1.8.0_141-cloudera/jre/lib/rt.jar:/root/hive_jdbc_client.jar:/root/hive-jdbc-3.1.2000.7.0.0.0-SNAPSHOT-standalone.jar
Executing show databases
default
information_schema
naveen
sys
Executing show tables
customers
sample_07
sample_08
web_logs
Using DatabaseMetadata APIs
Printing TABLE_TYPES
TABLE
VIEW
INDEX_TABLE
MATERIALIZED_VIEW
Printing Catalogs
Printing Schemas
default
information_schema
naveen
sys
Fetching Tables
[TABLE_NAME]:sample_07, [TABLE_TYPE]:TABLE, [SCHEMA]:default, [CATALOG]:,
[TABLE_NAME]:sample_08, [TABLE_TYPE]:TABLE, [SCHEMA]:default, [CATALOG]:,
[TABLE_NAME]:customers, [TABLE_TYPE]:TABLE, [SCHEMA]:default, [CATALOG]:,
[TABLE_NAME]:web_logs, [TABLE_TYPE]:TABLE, [SCHEMA]:default, [CATALOG]:,
[TABLE_NAME]:schemata, [TABLE_TYPE]:VIEW, [SCHEMA]:information_schema,
[CATALOG]:,
[TABLE_NAME]:tables, [TABLE_TYPE]:VIEW, [SCHEMA]:information_schema, [CATALOG]:,
[TABLE_NAME]:table_privileges, [TABLE_TYPE]:VIEW, [SCHEMA]:information_schema,
[CATALOG]:,
[TABLE_NAME]:columns, [TABLE_TYPE]:VIEW, [SCHEMA]:information_schema,
[CATALOG]:,
[TABLE_NAME]:column_privileges, [TABLE_TYPE]:VIEW, [SCHEMA]:information_schema,
[CATALOG]:,
[TABLE_NAME]:views, [TABLE_TYPE]:VIEW, [SCHEMA]:information_schema, [CATALOG]:,
[TABLE_NAME]:test, [TABLE_TYPE]:TABLE, [SCHEMA]:naveen, [CATALOG]:,
{code}
I have attached the JDBC client code that I executed to verify that the new
standalone jar executes fine.
> Hive 3.1 driver includes org.glassfish.jersey.* which can interfer with an
> application
> --------------------------------------------------------------------------------------
>
> Key: HIVE-22134
> URL: https://issues.apache.org/jira/browse/HIVE-22134
> Project: Hive
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 3.1.0
> Reporter: N Campbell
> Assignee: Naveen Gangam
> Priority: Major
> Attachments: HIVE-22134.patch
>
>
> An application that uses JAX-RS 1.1 can be broken by the Hive 3.1 standalone
> JAR.
> For example, an application is running in IBM Websphere Liberty Profile
> (WLP) which detects the classes packaged in the Apache Hive standalone JAR.
> This results in WLP assuming that the application is providing it's
> implementation and should not use the default in WLP.
> Can the Apache Hive JDBC team confirm why these classes are in the JAR.
> Can the Apache Hive JDBC team schedule to remove them if they are not
> mandatory.
> Can the Apache Hive JDBC team confirm which individual JAR files can be
> copied instead of the uber-standalone JAR which would not include these
> conflicting classes.
> This is the class which triggers the problem if all of the jersey stuff is
> deleted the issue will go away
> org.glassfish.jersey.server.internal.RuntimeDelegateImpl
> {{org.glassfish.jersey.*}}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
