[jira] [Updated] (HIVE-4568) Beeline needs to support resolving variables
[
https://issues.apache.org/jira/browse/HIVE-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brock Noland updated HIVE-4568:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk! Thank you for the review Thejas!
Beeline needs to support resolving variables
Key: HIVE-4568
URL: https://issues.apache.org/jira/browse/HIVE-4568
Project: Hive
Issue Type: Improvement
Affects Versions: 0.10.0
Reporter: Xuefu Zhang
Assignee: Xuefu Zhang
Fix For: 0.12.0
Attachments: HIVE-4568-1.patch, HIVE-4568-2.patch, HIVE-4568.3.patch,
HIVE-4568.4.patch, HIVE-4568.5.patch, HIVE-4568.6.patch, HIVE-4568.7.patch,
HIVE-4568.8.patch, HIVE-4568.patch
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:
{code}
hive --hivevar
INPUT=/user/jenkins/oozie.1371538916178/examples/input-data/table
--hivevar
OUTPUT=/user/jenkins/oozie.1371538916178/examples/output-data/hive
-f script.q
{code}
script.q makes use of hive variables:
{code}
CREATE EXTERNAL TABLE test (a INT) STORED AS TEXTFILE LOCATION '${INPUT}';
INSERT OVERWRITE DIRECTORY '${OUTPUT}' SELECT * FROM test;
{code}
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-4568) Beeline needs to support resolving variables
[
https://issues.apache.org/jira/browse/HIVE-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brock Noland updated HIVE-4568:
---
Fix Version/s: (was: 0.12.0)
0.13.0
Beeline needs to support resolving variables
Key: HIVE-4568
URL: https://issues.apache.org/jira/browse/HIVE-4568
Project: Hive
Issue Type: Improvement
Affects Versions: 0.10.0
Reporter: Xuefu Zhang
Assignee: Xuefu Zhang
Fix For: 0.13.0
Attachments: HIVE-4568-1.patch, HIVE-4568-2.patch, HIVE-4568.3.patch,
HIVE-4568.4.patch, HIVE-4568.5.patch, HIVE-4568.6.patch, HIVE-4568.7.patch,
HIVE-4568.8.patch, HIVE-4568.patch
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:
{code}
hive --hivevar
INPUT=/user/jenkins/oozie.1371538916178/examples/input-data/table
--hivevar
OUTPUT=/user/jenkins/oozie.1371538916178/examples/output-data/hive
-f script.q
{code}
script.q makes use of hive variables:
{code}
CREATE EXTERNAL TABLE test (a INT) STORED AS TEXTFILE LOCATION '${INPUT}';
INSERT OVERWRITE DIRECTORY '${OUTPUT}' SELECT * FROM test;
{code}
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-4568) Beeline needs to support resolving variables
[
https://issues.apache.org/jira/browse/HIVE-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xuefu Zhang updated HIVE-4568:
--
Attachment: HIVE-4568.8.patch
Beeline needs to support resolving variables
Key: HIVE-4568
URL: https://issues.apache.org/jira/browse/HIVE-4568
Project: Hive
Issue Type: Improvement
Affects Versions: 0.10.0
Reporter: Xuefu Zhang
Assignee: Xuefu Zhang
Fix For: 0.12.0
Attachments: HIVE-4568-1.patch, HIVE-4568-2.patch, HIVE-4568.3.patch,
HIVE-4568.4.patch, HIVE-4568.5.patch, HIVE-4568.6.patch, HIVE-4568.7.patch,
HIVE-4568.8.patch, HIVE-4568.patch
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:
{code}
hive --hivevar
INPUT=/user/jenkins/oozie.1371538916178/examples/input-data/table
--hivevar
OUTPUT=/user/jenkins/oozie.1371538916178/examples/output-data/hive
-f script.q
{code}
script.q makes use of hive variables:
{code}
CREATE EXTERNAL TABLE test (a INT) STORED AS TEXTFILE LOCATION '${INPUT}';
INSERT OVERWRITE DIRECTORY '${OUTPUT}' SELECT * FROM test;
{code}
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-4568) Beeline needs to support resolving variables
[
https://issues.apache.org/jira/browse/HIVE-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xuefu Zhang updated HIVE-4568:
--
Attachment: HIVE-4568.6.patch
Rename the patch to kick off test (again).
Beeline needs to support resolving variables
Key: HIVE-4568
URL: https://issues.apache.org/jira/browse/HIVE-4568
Project: Hive
Issue Type: Improvement
Affects Versions: 0.10.0
Reporter: Xuefu Zhang
Assignee: Xuefu Zhang
Fix For: 0.12.0
Attachments: HIVE-4568-1.patch, HIVE-4568-2.patch, HIVE-4568.3.patch,
HIVE-4568.4.patch, HIVE-4568.5.patch, HIVE-4568.6.patch, HIVE-4568.patch
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:
{code}
hive --hivevar
INPUT=/user/jenkins/oozie.1371538916178/examples/input-data/table
--hivevar
OUTPUT=/user/jenkins/oozie.1371538916178/examples/output-data/hive
-f script.q
{code}
script.q makes use of hive variables:
{code}
CREATE EXTERNAL TABLE test (a INT) STORED AS TEXTFILE LOCATION '${INPUT}';
INSERT OVERWRITE DIRECTORY '${OUTPUT}' SELECT * FROM test;
{code}
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-4568) Beeline needs to support resolving variables
[
https://issues.apache.org/jira/browse/HIVE-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xuefu Zhang updated HIVE-4568:
--
Attachment: HIVE-4568.7.patch
There seemed to be some merging issues with previous patches. Patch is updated
the latest is HIVE-4568.7.patch.
Beeline needs to support resolving variables
Key: HIVE-4568
URL: https://issues.apache.org/jira/browse/HIVE-4568
Project: Hive
Issue Type: Improvement
Affects Versions: 0.10.0
Reporter: Xuefu Zhang
Assignee: Xuefu Zhang
Fix For: 0.12.0
Attachments: HIVE-4568-1.patch, HIVE-4568-2.patch, HIVE-4568.3.patch,
HIVE-4568.4.patch, HIVE-4568.5.patch, HIVE-4568.6.patch, HIVE-4568.7.patch,
HIVE-4568.patch
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:
{code}
hive --hivevar
INPUT=/user/jenkins/oozie.1371538916178/examples/input-data/table
--hivevar
OUTPUT=/user/jenkins/oozie.1371538916178/examples/output-data/hive
-f script.q
{code}
script.q makes use of hive variables:
{code}
CREATE EXTERNAL TABLE test (a INT) STORED AS TEXTFILE LOCATION '${INPUT}';
INSERT OVERWRITE DIRECTORY '${OUTPUT}' SELECT * FROM test;
{code}
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-4568) Beeline needs to support resolving variables
[
https://issues.apache.org/jira/browse/HIVE-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xuefu Zhang updated HIVE-4568:
--
Attachment: HIVE-4568.5.patch
patch 5 is the same as 4. Reattach it to kick off test.
Beeline needs to support resolving variables
Key: HIVE-4568
URL: https://issues.apache.org/jira/browse/HIVE-4568
Project: Hive
Issue Type: Improvement
Affects Versions: 0.10.0
Reporter: Xuefu Zhang
Assignee: Xuefu Zhang
Fix For: 0.12.0
Attachments: HIVE-4568-1.patch, HIVE-4568-2.patch, HIVE-4568.3.patch,
HIVE-4568.4.patch, HIVE-4568.5.patch, HIVE-4568.patch
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:
{code}
hive --hivevar
INPUT=/user/jenkins/oozie.1371538916178/examples/input-data/table
--hivevar
OUTPUT=/user/jenkins/oozie.1371538916178/examples/output-data/hive
-f script.q
{code}
script.q makes use of hive variables:
{code}
CREATE EXTERNAL TABLE test (a INT) STORED AS TEXTFILE LOCATION '${INPUT}';
INSERT OVERWRITE DIRECTORY '${OUTPUT}' SELECT * FROM test;
{code}
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-4568) Beeline needs to support resolving variables
[
https://issues.apache.org/jira/browse/HIVE-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xuefu Zhang updated HIVE-4568:
--
Attachment: HIVE-4568.4.patch
Beeline needs to support resolving variables
Key: HIVE-4568
URL: https://issues.apache.org/jira/browse/HIVE-4568
Project: Hive
Issue Type: Improvement
Affects Versions: 0.10.0
Reporter: Xuefu Zhang
Assignee: Xuefu Zhang
Fix For: 0.12.0
Attachments: HIVE-4568-1.patch, HIVE-4568-2.patch, HIVE-4568.3.patch,
HIVE-4568.4.patch, HIVE-4568.patch
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:
{code}
hive --hivevar
INPUT=/user/jenkins/oozie.1371538916178/examples/input-data/table
--hivevar
OUTPUT=/user/jenkins/oozie.1371538916178/examples/output-data/hive
-f script.q
{code}
script.q makes use of hive variables:
{code}
CREATE EXTERNAL TABLE test (a INT) STORED AS TEXTFILE LOCATION '${INPUT}';
INSERT OVERWRITE DIRECTORY '${OUTPUT}' SELECT * FROM test;
{code}
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-4568) Beeline needs to support resolving variables
[
https://issues.apache.org/jira/browse/HIVE-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xuefu Zhang updated HIVE-4568:
--
Attachment: HIVE-4568.3.patch
Patch is updated based on review feedback.
Beeline needs to support resolving variables
Key: HIVE-4568
URL: https://issues.apache.org/jira/browse/HIVE-4568
Project: Hive
Issue Type: Improvement
Affects Versions: 0.10.0
Reporter: Xuefu Zhang
Assignee: Xuefu Zhang
Fix For: 0.12.0
Attachments: HIVE-4568-1.patch, HIVE-4568-2.patch, HIVE-4568.3.patch,
HIVE-4568.patch
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:
{code}
hive --hivevar
INPUT=/user/jenkins/oozie.1371538916178/examples/input-data/table
--hivevar
OUTPUT=/user/jenkins/oozie.1371538916178/examples/output-data/hive
-f script.q
{code}
script.q makes use of hive variables:
{code}
CREATE EXTERNAL TABLE test (a INT) STORED AS TEXTFILE LOCATION '${INPUT}';
INSERT OVERWRITE DIRECTORY '${OUTPUT}' SELECT * FROM test;
{code}
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-4568) Beeline needs to support resolving variables
[
https://issues.apache.org/jira/browse/HIVE-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xuefu Zhang updated HIVE-4568:
--
Priority: Major (was: Minor)
Beeline needs to support resolving variables
Key: HIVE-4568
URL: https://issues.apache.org/jira/browse/HIVE-4568
Project: Hive
Issue Type: Improvement
Affects Versions: 0.10.0
Reporter: Xuefu Zhang
Assignee: Xuefu Zhang
Fix For: 0.12.0
Attachments: HIVE-4568-1.patch, HIVE-4568.patch
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:
{code}
hive --hivevar
INPUT=/user/jenkins/oozie.1371538916178/examples/input-data/table
--hivevar
OUTPUT=/user/jenkins/oozie.1371538916178/examples/output-data/hive
-f script.q
{code}
script.q makes use of hive variables:
{code}
CREATE EXTERNAL TABLE test (a INT) STORED AS TEXTFILE LOCATION '${INPUT}';
INSERT OVERWRITE DIRECTORY '${OUTPUT}' SELECT * FROM test;
{code}
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-4568) Beeline needs to support resolving variables
[
https://issues.apache.org/jira/browse/HIVE-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xuefu Zhang updated HIVE-4568:
--
Attachment: HIVE-4568-2.patch
Patch is updated to reflect its dependency on HIVE-5131.
Beeline needs to support resolving variables
Key: HIVE-4568
URL: https://issues.apache.org/jira/browse/HIVE-4568
Project: Hive
Issue Type: Improvement
Affects Versions: 0.10.0
Reporter: Xuefu Zhang
Assignee: Xuefu Zhang
Fix For: 0.12.0
Attachments: HIVE-4568-1.patch, HIVE-4568-2.patch, HIVE-4568.patch
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:
{code}
hive --hivevar
INPUT=/user/jenkins/oozie.1371538916178/examples/input-data/table
--hivevar
OUTPUT=/user/jenkins/oozie.1371538916178/examples/output-data/hive
-f script.q
{code}
script.q makes use of hive variables:
{code}
CREATE EXTERNAL TABLE test (a INT) STORED AS TEXTFILE LOCATION '${INPUT}';
INSERT OVERWRITE DIRECTORY '${OUTPUT}' SELECT * FROM test;
{code}
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-4568) Beeline needs to support resolving variables
[
https://issues.apache.org/jira/browse/HIVE-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xuefu Zhang updated HIVE-4568:
--
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:
{code}
hive --hivevar
INPUT=/user/jenkins/oozie.1371538916178/examples/input-data/table
--hivevar
OUTPUT=/user/jenkins/oozie.1371538916178/examples/output-data/hive
-f script.q
{code}
script.q makes use of hive variables:
{code}
CREATE EXTERNAL TABLE test (a INT) STORED AS TEXTFILE LOCATION '${INPUT}';
INSERT OVERWRITE DIRECTORY '${OUTPUT}' SELECT * FROM test;
{code}
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.
was:Beeline currently doesn't support variable (system, env, etc)
substitution as hive client does. Supporting this feature will certainly make
it more usable.
Beeline needs to support resolving variables
Key: HIVE-4568
URL: https://issues.apache.org/jira/browse/HIVE-4568
Project: Hive
Issue Type: Improvement
Affects Versions: 0.10.0
Reporter: Xuefu Zhang
Assignee: Xuefu Zhang
Priority: Minor
Attachments: HIVE-4568.patch
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:
{code}
hive --hivevar
INPUT=/user/jenkins/oozie.1371538916178/examples/input-data/table
--hivevar
OUTPUT=/user/jenkins/oozie.1371538916178/examples/output-data/hive
-f script.q
{code}
script.q makes use of hive variables:
{code}
CREATE EXTERNAL TABLE test (a INT) STORED AS TEXTFILE LOCATION '${INPUT}';
INSERT OVERWRITE DIRECTORY '${OUTPUT}' SELECT * FROM test;
{code}
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-4568) Beeline needs to support resolving variables
[
https://issues.apache.org/jira/browse/HIVE-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xuefu Zhang updated HIVE-4568:
--
Fix Version/s: 0.12.0
Status: Patch Available (was: Open)
Beeline needs to support resolving variables
Key: HIVE-4568
URL: https://issues.apache.org/jira/browse/HIVE-4568
Project: Hive
Issue Type: Improvement
Affects Versions: 0.10.0
Reporter: Xuefu Zhang
Assignee: Xuefu Zhang
Priority: Minor
Fix For: 0.12.0
Attachments: HIVE-4568-1.patch, HIVE-4568.patch
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:
{code}
hive --hivevar
INPUT=/user/jenkins/oozie.1371538916178/examples/input-data/table
--hivevar
OUTPUT=/user/jenkins/oozie.1371538916178/examples/output-data/hive
-f script.q
{code}
script.q makes use of hive variables:
{code}
CREATE EXTERNAL TABLE test (a INT) STORED AS TEXTFILE LOCATION '${INPUT}';
INSERT OVERWRITE DIRECTORY '${OUTPUT}' SELECT * FROM test;
{code}
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-4568) Beeline needs to support resolving variables
[
https://issues.apache.org/jira/browse/HIVE-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xuefu Zhang updated HIVE-4568:
--
Attachment: HIVE-4568-1.patch
Beeline needs to support resolving variables
Key: HIVE-4568
URL: https://issues.apache.org/jira/browse/HIVE-4568
Project: Hive
Issue Type: Improvement
Affects Versions: 0.10.0
Reporter: Xuefu Zhang
Assignee: Xuefu Zhang
Priority: Minor
Attachments: HIVE-4568-1.patch, HIVE-4568.patch
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:
{code}
hive --hivevar
INPUT=/user/jenkins/oozie.1371538916178/examples/input-data/table
--hivevar
OUTPUT=/user/jenkins/oozie.1371538916178/examples/output-data/hive
-f script.q
{code}
script.q makes use of hive variables:
{code}
CREATE EXTERNAL TABLE test (a INT) STORED AS TEXTFILE LOCATION '${INPUT}';
INSERT OVERWRITE DIRECTORY '${OUTPUT}' SELECT * FROM test;
{code}
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-4568) Beeline needs to support resolving variables
[ https://issues.apache.org/jira/browse/HIVE-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuefu Zhang updated HIVE-4568: -- Fix Version/s: (was: 0.11.1) Beeline needs to support resolving variables Key: HIVE-4568 URL: https://issues.apache.org/jira/browse/HIVE-4568 Project: Hive Issue Type: Improvement Affects Versions: 0.10.0 Reporter: Xuefu Zhang Assignee: Xuefu Zhang Priority: Minor Attachments: HIVE-4568.patch Beeline currently doesn't support variable (system, env, etc) substitution as hive client does. Supporting this feature will certainly make it more usable. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-4568) Beeline needs to support resolving variables
[ https://issues.apache.org/jira/browse/HIVE-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuefu Zhang updated HIVE-4568: -- Attachment: HIVE-4568.patch Beeline needs to support resolving variables Key: HIVE-4568 URL: https://issues.apache.org/jira/browse/HIVE-4568 Project: Hive Issue Type: Improvement Affects Versions: 0.10.0 Reporter: Xuefu Zhang Assignee: Xuefu Zhang Priority: Minor Attachments: HIVE-4568.patch Beeline currently doesn't support variable (system, env, etc) substitution as hive client does. Supporting this feature will certainly make it more usable. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-4568) Beeline needs to support resolving variables
[ https://issues.apache.org/jira/browse/HIVE-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuefu Zhang updated HIVE-4568: -- Fix Version/s: 0.11.1 Status: Patch Available (was: Open) Attached patch is to address the issue. Beeline needs to support resolving variables Key: HIVE-4568 URL: https://issues.apache.org/jira/browse/HIVE-4568 Project: Hive Issue Type: Improvement Affects Versions: 0.10.0 Reporter: Xuefu Zhang Assignee: Xuefu Zhang Priority: Minor Fix For: 0.11.1 Attachments: HIVE-4568.patch Beeline currently doesn't support variable (system, env, etc) substitution as hive client does. Supporting this feature will certainly make it more usable. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
