You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hive.apache.org by "Szehon Ho (JIRA)" <ji...@apache.org> on 2018/06/01 17:46:00 UTC

[jira] [Created] (HIVE-19767) HiveServer2 should take hiveconf for non Hive properties

Szehon Ho created HIVE-19767:
--------------------------------

             Summary: HiveServer2 should take hiveconf for non Hive properties
                 Key: HIVE-19767
                 URL: https://issues.apache.org/jira/browse/HIVE-19767
             Project: Hive
          Issue Type: Bug
            Reporter: Szehon Ho
            Assignee: Szehon Ho


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:
{noformat}
./bin/hive --hiveconf a=b
hive> set a;
a=b {noformat}
HiveServer2 behavior:
{noformat}
./bin/hiveserver2 --hiveconf a=b
beeline> set a;
+-----------------+
|       set       |
+-----------------+
| a is undefined  |
+-----------------+{noformat}
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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)