[HIVE-22134] Hive 3.1 driver includes org.glassfish.jersey.* which can interfer with an application

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.1.0
• Fix Version/s: 4.0.0-alpha-1
• Component/s: JDBC
• Assignee: Naveen Gangam
• Reporter: N Campbell
• Created: 21/Aug/19 17:52
• Updated: 17/Nov/22 08:51
• Resolved: 26/Aug/19 21:41

Description

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.*

Issue Links

• links to: ReviewBoard