[
https://issues.apache.org/jira/browse/HIVE-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071318#comment-13071318
]
Vaibhav Aggarwal commented on HIVE-2020:
----------------------------------------
I propose to use -d, --define to define Hive variables.
Amazon ElasticMapreduce is already using this notation for hive variables and
variable substitution.
This approach would also clearly separate use of -hiveconf from -d or --define
which would be used to purely set hive variables.
This would also maintain consistency for Hive users.
> Create a separate namespace for Hive variables
> ----------------------------------------------
>
> Key: HIVE-2020
> URL: https://issues.apache.org/jira/browse/HIVE-2020
> Project: Hive
> Issue Type: Improvement
> Components: Query Processor
> Reporter: Carl Steinbach
>
> Support for variable substitution was added in HIVE-1096. However, variable
> substitution was implemented by reusing the HiveConf namespace, so there is
> no separation between Hive configuration properties and Hive variables.
> This ticket encompasses the following enhancements:
> * Create a separate namespace for managing Hive variables.
> * Add support for setting variables on the command line via '-hivevar x=y'
> * Add support for setting variables through the CLI via 'var x=y'
> * Add support for referencing variables in statements using either
> '${hivevar:var_name}' or '${var_name}'
> * Provide a means for differentiating between hiveconf, hivevar, system, and
> environment properties in the output of 'set -v'
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
