[
https://issues.apache.org/jira/browse/HIVE-6045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13852167#comment-13852167
]
Szehon Ho commented on HIVE-6045:
---------------------------------
I don't see any immediate changes. Do you remember if the parsing used to
expect '&' character? I believe that would be the only way it would have
worked, but I guess there was never a unit test for this case.
I will take a look at effort to move the test to /itests/hive-unit , there are
a few tests about null as empty string that seem broken when I ran it, I will
have to take a look.
> 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)
