[HIVE-19767] HiveServer2 should take hiveconf for non Hive properties

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.2, 2.3.2, 3.0.0
• Fix Version/s: 4.0.0-alpha-1
• Assignee: Szehon Ho
• Reporter: Szehon Ho
• Created: 01/Jun/18 17:45
• Updated: 17/Nov/22 08:54
• Resolved: 17/Aug/18 09:36

Description

The -hiveconf command line option works in HiveServer2 with properties in HiveConf.java, but not so well with other properties (like mapred properties or spark properties to control underlying execution engine, or custom properties understood by custom listeners)

It is inconsistent with HiveCLI.

HiveCLI behavior:

./bin/hive --hiveconf a=b
hive> set a;
a=b 

HiveServer2 behavior:

./bin/hiveserver2 --hiveconf a=b
beeline> set a;
+-----------------+
|       set       |
+-----------------+
| a is undefined  |
+-----------------+

Although it is possible to set up hive-site.xml or even mapred-site.xml to fill in the relevant properties, it is more convenient when testing HS2 with different configuration to be able to use --hiveconf to change on the fly.

Issue Links

• is related to: HIVE-4292 hiveserver2 should support -hiveconf commandline parameter