[
https://issues.apache.org/jira/browse/KUDU-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17124336#comment-17124336
]
Grant Henke commented on KUDU-2268:
-----------------------------------
I think this was resolved via
https://github.com/apache/kudu/commit/ce0db915787b58a79109e6faecc6f1daef9f2850
(though the commit references the wrong jira)
> Sync client exceptions don't show appropriate call stack
> --------------------------------------------------------
>
> Key: KUDU-2268
> URL: https://issues.apache.org/jira/browse/KUDU-2268
> Project: Kudu
> Issue Type: Improvement
> Components: client, java
> Reporter: Todd Lipcon
> Priority: Major
>
> Currently if you use the sync client and try to connect to the cluster but
> get some error like an authentication failure, the call stack in the
> resulting exception is entirely within Kudu/Netty code. It doesn't show you
> where your actual error is. We should fix up the call stacks before throwing
> errors in the sync client.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
