[
https://issues.apache.org/jira/browse/HIVE-10048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14372536#comment-14372536
]
Hive QA commented on HIVE-10048:
--------------------------------
{color:green}Overall{color}: +1 all checks pass
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12706111/HIVE-10048.1.patch
{color:green}SUCCESS:{color} +1 7818 tests passed
Test results:
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/3103/testReport
Console output:
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/3103/console
Test logs:
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-3103/
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: 12706111 - PreCommit-HIVE-TRUNK-Build
> JDBC - Support SSL encryption regardless of Authentication mechanism
> --------------------------------------------------------------------
>
> Key: HIVE-10048
> URL: https://issues.apache.org/jira/browse/HIVE-10048
> Project: Hive
> Issue Type: Improvement
> Components: JDBC
> Affects Versions: 1.0.0
> Reporter: Mubashir Kazia
> Labels: newbie, patch
> Fix For: 1.2.0
>
> Attachments: HIVE-10048.1.patch
>
>
> JDBC driver currently only supports SSL Transport if the Authentication
> mechanism is SASL Plain with username and password. SSL transport should be
> decoupled from Authentication mechanism. If the customer chooses to do
> Kerberos Authentication and SSL encryption over the wire it should be
> supported. The Server side already supports this but the driver does not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
