You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Francisco Guerrero (Jira)" <ji...@apache.org> on 2020/06/15 17:15:00 UTC
[jira] [Created] (HIVE-23700) HiveConf static initialization fails
when JAR URI is opaque
Francisco Guerrero created HIVE-23700:
-----------------------------------------
Summary: HiveConf static initialization fails when JAR URI is opaque
Key: HIVE-23700
URL: https://issues.apache.org/jira/browse/HIVE-23700
Project: Hive
Issue Type: Bug
Components: Hive
Affects Versions: 2.3.7, 3.1.2
Reporter: Francisco Guerrero
HiveConf static initialization fails when the jar URI is opaque, for example when it's embedded as a fat jar in a spring boot application. Then initialization of the HiveConf static block fails and the HiveConf class does not get classloaded. The opaque URI in my case looks like this _jar:file:/usr/local/server/some-service-jar.jar!/BOOT-INF/lib/hive-common-2.3.7.jar!/_
HiveConf#findConfigFile should be able to handle `IllegalArgumentException` when the jar `URI` provided to `File` throws the exception.
To surface this issue three conditions need to be met.
1. hive-site.xml should not be on the classpath
2. hive-site.xml should not be on "HIVE_CONF_DIR"
3. hive-site.xml should not be on "HIVE_HOME"
--
This message was sent by Atlassian Jira
(v8.3.4#803005)