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

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

GitHub user parthchandra opened a pull request:

    https://github.com/apache/drill/pull/992

    DRILL-5873: (C++ Client) Improve SASL error reporting.

    @sohami what do you think? I overrode the SASL_NOMECH error message. The 
message from the SASL library is very unfriendly.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/parthchandra/drill DRILL-5873

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/drill/pull/992.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #992
    
----
commit 31e71147c37a7e37348dfae323d894114204c8dd
Author: Parth Chandra <[email protected]>
Date:   2017-10-13T18:00:31Z

    DRILL-5873: (C++ Client) Improve SASL error reporting.

----


> Drill C++ Client should throw proper/complete error message for the ODBC 
> driver to consume
> ------------------------------------------------------------------------------------------
>
>                 Key: DRILL-5873
>                 URL: https://issues.apache.org/jira/browse/DRILL-5873
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Client - C++
>            Reporter: Krystal
>            Assignee: Parth Chandra
>
> The Drill C++ Client should throw a proper/complete error message for the 
> driver to utilize.
> The ODBC driver is directly outputting the exception message thrown by the 
> client by calling the getError() API after the connect() API has failed with 
> an error status.
> For the Java client, similar logic is hard coded at 
> https://github.com/apache/drill/blob/1.11.0/exec/java-exec/src/main/java/org/apache/drill/exec/rpc/user/UserClient.java#L247.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to