[HIVE-23700] HiveConf static initialization fails when JAR URI is opaque

• Type: Bug
• Status: Patch Available
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 2.3.7
• Component/s: Hive
• Labels: pull-request-available
• Assignee: Francisco Guerrero
• Reporter: Francisco Guerrero
• Created: 15/Jun/20 17:14
• Updated: 09/Oct/20 20:42

Description

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"

Issue Links

• is duplicated by: HIVE-21692 Hiveconf initiated in "fat jar" fails to retrieve configuration from hive-common jar
• links to: GitHub Pull Request #1138
• links to: GitHub Pull Request #1139
• links to: GitHub Pull Request #1140
• links to: GitHub Pull Request #1240