hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Szehon Ho (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-19767) HiveServer2 should take hiveconf for non Hive properties
Date Sat, 11 Aug 2018 02:09:00 GMT

     [ https://issues.apache.org/jira/browse/HIVE-19767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Szehon Ho updated HIVE-19767:
-----------------------------
    Attachment: HIVE-19767.3.patch

> HiveServer2 should take hiveconf for non Hive properties
> --------------------------------------------------------
>
>                 Key: HIVE-19767
>                 URL: https://issues.apache.org/jira/browse/HIVE-19767
>             Project: Hive
>          Issue Type: Improvement
>    Affects Versions: 1.2.2, 3.0.0, 2.3.2
>            Reporter: Szehon Ho
>            Assignee: Szehon Ho
>            Priority: Major
>         Attachments: HIVE-19767.2.patch, HIVE-19767.3.patch, 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)

Mime
View raw message