[
https://issues.apache.org/jira/browse/HIVE-28308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17853584#comment-17853584
]
Zhihua Deng commented on HIVE-28308:
------------------------------------
I think the org.apache.hive:hive-jdbc:4.0.0 behaviors as expected, in your case
please try
{noformat}
<dependency>
<groupId>org.apache.hive</groupId>
<artifactId>hive-jdbc</artifactId>
<classifier>standalone</classifier>
<version>4.0.0</version>
</dependency>{noformat}
it would no need to add extra dependencies, but I'm not sure if it works well
with the embedded HS2.
However there are some missing classes when I try using this standalone jar, I
filed a Jira HIVE-28315 to address the problem.
> The module `org.apache.hive:hive-jdbc:4.0.0` unintuitively removed all
> dependencies under the Compile Scope
> -----------------------------------------------------------------------------------------------------------
>
> Key: HIVE-28308
> URL: https://issues.apache.org/jira/browse/HIVE-28308
> Project: Hive
> Issue Type: Bug
> Reporter: Qiheng He
> Priority: Major
>
> - The module *org.apache.hive:hive-jdbc:4.0.0* unintuitively removed all
> dependencies under the Compile Scope.
> - Comparing the dependencies listed at
> [https://central.sonatype.com/artifact/org.apache.hive/hive-jdbc/4.0.0/dependencies]
> with those at
> [https://central.sonatype.com/artifact/org.apache.hive/hive-jdbc/3.1.3/dependencies]
> , it becomes apparent that *org.apache.hive:hive-jdbc:4.0.0* includes only
> test dependencies. This results in the need to manually add additional
> dependencies when utilizing the HiveServer2 JDBC Driver.
> -
> {code:xml}
> <dependency>
> <groupId>org.apache.hive</groupId>
> <artifactId>hive-jdbc</artifactId>
> <version>4.0.0</version>
> </dependency>
> <dependency>
> <groupId>org.apache.hive</groupId>
> <artifactId>hive-service</artifactId>
> <version>4.0.0</version>
> <exclusions>
> <exclusion>
> <groupId>org.apache.logging.log4j</groupId>
> <artifactId>log4j-slf4j-impl</artifactId>
> </exclusion>
> <exclusion>
> <groupId>org.slf4j</groupId>
> <artifactId>slf4j-reload4j</artifactId>
> </exclusion>
> <exclusion>
> <groupId>org.apache.logging.log4j</groupId>
> <artifactId>log4j-web</artifactId>
> </exclusion>
> <exclusion>
> <groupId>org.apache.logging.log4j</groupId>
> <artifactId>log4j-core</artifactId>
> </exclusion>
> <exclusion>
> <groupId>org.apache.logging.log4j</groupId>
> <artifactId>log4j-api</artifactId>
> </exclusion>
> <exclusion>
> <groupId>org.apache.logging.log4j</groupId>
> <artifactId>log4j-1.2-api</artifactId>
> </exclusion>
> </exclusions>
> </dependency>
> <dependency>
> <groupId>org.apache.hadoop</groupId>
> <artifactId>hadoop-client-runtime</artifactId>
> <version>3.3.6</version>
> </dependency>
> {code}
> - More early surveys come from
> https://github.com/apache/shardingSphere/pull/31526 and
> https://github.com/dbeaver/dbeaver/issues/22777 . I personally think this is
> not a reasonable phenomenon.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
