[HIVE-4568] Beeline needs to support resolving variables

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.10.0
• Fix Version/s: 0.13.0
• Assignee: Xuefu Zhang
• Reporter: Xuefu Zhang
• Created: 15/May/13 22:47
• Updated: 17/Dec/13 18:58
• Resolved: 20/Sep/13 16:07

Description

Previous Hive CLI allows user to specify hive variables at the command line using option "--hivevar". In user's script, reference to a hive variable will be substituted with the value of the variable. In such way, user can parameterize his/her script and invoke the script with different hive variable values. The following script is one usage:

hive --hivevar
     INPUT=/user/jenkins/oozie.1371538916178/examples/input-data/table
     --hivevar
     OUTPUT=/user/jenkins/oozie.1371538916178/examples/output-data/hive
     -f script.q

script.q makes use of hive variables:

CREATE EXTERNAL TABLE test (a INT) STORED AS TEXTFILE LOCATION '${INPUT}';
INSERT OVERWRITE DIRECTORY '${OUTPUT}' SELECT * FROM test;

However, after upgrade to hiveserver2 and beeline, this functionality is missing. Beeline doesn't take --hivevar option, and any hive variable isn't passed to server so it cannot be used for substitution.

This JIRA is to address this issue, providing a backward compatible behavior at Beeline.

Issue Links

• depends upon: HIVE-5131 JDBC client's hive variables are not passed to HS2
• incorporates: HIVE-6045 Beeline hivevars is broken for more than one hivevar
• links to: Review Board