[ 
https://issues.apache.org/jira/browse/HIVE-19568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16555395#comment-16555395
 ] 

Hive QA commented on HIVE-19568:
--------------------------------



Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12932985/HIVE-19568.01.patch

{color:red}ERROR:{color} -1 due to build exiting with an error

Test results: 
https://builds.apache.org/job/PreCommit-HIVE-Build/12847/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/12847/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-12847/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Tests exited with: Exception: Patch URL 
https://issues.apache.org/jira/secure/attachment/12932985/HIVE-19568.01.patch 
was found in seen patch url's cache and a test was probably run already on it. 
Aborting...
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12932985 - PreCommit-HIVE-Build

> Active/Passive HS2 HA: Disallow direct connection to passive HS2 instance
> -------------------------------------------------------------------------
>
>                 Key: HIVE-19568
>                 URL: https://issues.apache.org/jira/browse/HIVE-19568
>             Project: Hive
>          Issue Type: Bug
>          Components: HiveServer2
>    Affects Versions: 3.1.0
>            Reporter: Prasanth Jayachandran
>            Assignee: Sergey Shelukhin
>            Priority: Major
>         Attachments: HIVE-19568.01.patch, HIVE-19568.patch
>
>
> The recommended usage for clients when connecting to HS2 with Active/Passive 
> HA configuration is via ZK service discovery URL. But some applications do 
> not support ZK service discovery in which case they use direct URL to connect 
> to HS2 instance. If direct connection is to passive HS2 instance, the 
> connection should be dropped with proper error message. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to