You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Chaoyu Tang (JIRA)" <ji...@apache.org> on 2015/11/05 14:55:27 UTC
[jira] [Updated] (HIVE-12346) Internally used variables in HiveConf
should not be settable via command
[ https://issues.apache.org/jira/browse/HIVE-12346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chaoyu Tang updated HIVE-12346:
-------------------------------
Attachment: HIVE-12346.patch
Add the internally used variables to a HiveConf HIVE_CONF_INTERNAL_VARIABLE_LIST, which will be a part of its restricted list.
> Internally used variables in HiveConf should not be settable via command
> ------------------------------------------------------------------------
>
> Key: HIVE-12346
> URL: https://issues.apache.org/jira/browse/HIVE-12346
> Project: Hive
> Issue Type: Bug
> Components: Configuration
> Affects Versions: 1.2.1
> Reporter: Chaoyu Tang
> Assignee: Chaoyu Tang
> Attachments: HIVE-12346.patch
>
>
> Some HiveConf variables such as hive.added.jars.path are only for internal use and should not be settable via set command.
> We saw a lot of cases that users mistakenly set these variables using set command despite some of them have been documented as "internal parameter" in Hive. The command usually succeeds but it sometimes does not effect, which causes some confusions. For example, the hive.added.jars.path can be set via set command but it is sometimes overridden by session resource jars during runtime.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)