[
https://issues.apache.org/jira/browse/HIVE-6045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13851296#comment-13851296
]
Hive QA commented on HIVE-6045:
-------------------------------
{color:green}Overall{color}: +1 all checks pass
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12619206/HIVE-6045.1.patch
{color:green}SUCCESS:{color} +1 4791 tests passed
Test results:
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/677/testReport
Console output:
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/677/console
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12619206
> Beeline hivevars is broken for more than one hivevar
> ----------------------------------------------------
>
> Key: HIVE-6045
> URL: https://issues.apache.org/jira/browse/HIVE-6045
> Project: Hive
> Issue Type: Bug
> Components: CLI
> Affects Versions: 0.13.0
> Reporter: Szehon Ho
> Assignee: Szehon Ho
> Attachments: HIVE-6045.1.patch, HIVE-6045.patch
>
>
> HIVE-4568 introduced --hivevar flag. But if you specify more than one
> hivevar, for example
> {code}
> beeline --hivevar file1=/user/szehon/file1 --hivevar file2=/user/szehon/file2
> {code}
> then the variables during runtime get mangled to evaluate to:
> {code}
> file1=/user/szehon/file1&file2=/user/szehon/file2
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
