hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-13044) Enable TLS encryption to HMS backend database
Date Sat, 20 Feb 2016 18:45:18 GMT


Hive QA commented on HIVE-13044:

Here are the results of testing the latest attachment:

{color:red}ERROR:{color} -1 due to no test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 2 failed/errored test(s), 9815 tests executed
*Failed tests:*

Test results:
Console output:
Test logs:

Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 2 tests failed

This message is automatically generated.

ATTACHMENT ID: 12788746 - PreCommit-HIVE-TRUNK-Build

> Enable TLS encryption to HMS backend database
> ---------------------------------------------
>                 Key: HIVE-13044
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>          Components: Metastore
>    Affects Versions: 2.1.0
>            Reporter: Aihua Xu
>            Assignee: Aihua Xu
>         Attachments: HIVE-13044.1.patch, HIVE-13044.2.patch
> When the database like mysql enables TLS/SSL encryption, we should provide some configuration
properties like the ones to HS2 to enable that. Right now, I think we can enable that through
javaopts and connection url.

This message was sent by Atlassian JIRA

View raw message