[
https://issues.apache.org/jira/browse/HIVE-6217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13875254#comment-13875254
]
Hive QA commented on HIVE-6217:
-------------------------------
{color:green}Overall{color}: +1 all checks pass
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12623697/HIVE-6217.patch
{color:green}SUCCESS:{color} +1 4940 tests passed
Test results:
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/948/testReport
Console output:
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/948/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: 12623697
> Refactor Beeline's JDBC connection to use property map instead of long url
> --------------------------------------------------------------------------
>
> Key: HIVE-6217
> URL: https://issues.apache.org/jira/browse/HIVE-6217
> Project: Hive
> Issue Type: Improvement
> Components: CLI, JDBC
> Affects Versions: 0.12.0
> Reporter: Xuefu Zhang
> Assignee: Xuefu Zhang
> Attachments: HIVE-6217.patch
>
>
> To make a connection to HiverServer2, currently Beeline constructs a long url
> that contains hiveconf and hivevariables. At JDBC driver side, it parses the
> url into individual maps. Constructing and decomposing the url is complicated
> and unnecessary, using a different method from JDBC DriverManager that takes
> a property map makes the logic simpler, especially when hiveconf and hivevar
> variables can also come from Beeline command line in addition to those in
> connection url.
> This is identified in and required by HIVE-6173.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
