Mailing-List: contact issues-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Date: Fri, 3 Mar 2017 07:01:45 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: issues@drill.apache.org
Message-ID: <JIRA.13047820.1488492046000.51723.1488524505309@Atlassian.JIRA>
In-Reply-To: <JIRA.13047820.1488492046000@Atlassian.JIRA>
References: <JIRA.13047820.1488492046000@Atlassian.JIRA> <JIRA.13047820.1488492046574@jira-lw-us.apache.org>
Subject: [jira] [Commented] (DRILL-5311) C++ connector connect doesn't wait
 for handshake to complete
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 03 Mar 2017 07:01:51 -0000


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

ASF GitHub Bot commented on DRILL-5311:
---------------------------------------

Github user sudheeshkatkam commented on the issue:

    https://github.com/apache/drill/pull/770
  
    +1


> C++ connector connect doesn't wait for handshake to complete
> ------------------------------------------------------------
>
>                 Key: DRILL-5311
>                 URL: https://issues.apache.org/jira/browse/DRILL-5311
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Client - C++
>            Reporter: Laurent Goujon
>
> The C++ connector connect methods returns okay as soon as the tcp connection is succesfully established between client and server, and the handshake message is sent. However it doesn't wait for handshake to have completed.
> The consequence is that if handshake failed, the error is deferred to the first query, which might be unexpected by the application.
> I believe that validateHanshake method in drillClientImpl should wait for the handshake to complete, as it seems a bit more saner...


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)