[
https://issues.apache.org/jira/browse/HIVE-22134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16914547#comment-16914547
]
Thejas M Nair commented on HIVE-22134:
--------------------------------------
+1
[~ngangam]
Can you also please verify that it works with a kerberos enabled cluster ?
(more jars are required for kerberos than non-kerberos).
> 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)
