hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-6217) Refactor Beeline's JDBC connection to use property map instead of long url
Date Thu, 30 Jan 2014 12:58:10 GMT


Hive QA commented on HIVE-6217:

{color:green}Overall{color}: +1 all checks pass

Here are the results of testing the latest attachment:

{color:green}SUCCESS:{color} +1 4972 tests passed

Test results:
Console output:

Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase

This message is automatically generated.


> Refactor Beeline's JDBC connection to use property map instead of long url
> --------------------------------------------------------------------------
>                 Key: HIVE-6217
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>          Components: CLI, JDBC
>    Affects Versions: 0.12.0
>            Reporter: Xuefu Zhang
>            Assignee: Xuefu Zhang
>         Attachments: HIVE-6217.1.patch, HIVE-6217.1.patch, HIVE-6217.1.patch, 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
> This is identified in and required by HIVE-6173. 

This message was sent by Atlassian JIRA

View raw message