[
https://issues.apache.org/jira/browse/HIVE-19767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16562162#comment-16562162
]
Szehon Ho commented on HIVE-19767:
----------------------------------
Hi Aihua, thanks for looking at this patch! I can set it in the session, but
to me it would be nice to set some permanent properties for the whole
HiveServer2, not tied to a session, and as to your suggestion, I would like to
start HiveServer2 and not a beeline with embedded HiveServer2. In our
use-case, we have some custom listener plugins that take in some properties not
listed in HiveConf, what do you think?
> 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
> Affects Versions: 1.2.2, 3.0.0, 2.3.2
> Reporter: Szehon Ho
> Assignee: Szehon Ho
> Priority: Major
> Attachments: HIVE-19767.patch
>
>
> 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)
