[
https://issues.apache.org/jira/browse/HIVE-6045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Szehon Ho updated HIVE-6045:
----------------------------
Attachment: HIVE-6045.1.patch
Today the hive-var is broken because of the following:
1. Beeline constructs jdbc url fragment of hive-var with '&' delimiter
2. JDBC uses ';' delimiter to parse this hive-var fragment.
Original patch had changed JDBC parsing regex (part 2) to expect '&'. But some
test cases were manually constructing JDBC url's with ';' as delimiter and
checking the parsing works on that. One option is the change the test, which
should be fine for JDBC URL backward-compatibility as this is new feature for
0.13.
But still I decided to minimize the impact and choose an alternate fix (part
1), so that beeline constructs URL fragment with ';' delimiter.
> 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)
