[
https://issues.apache.org/jira/browse/KUDU-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Henke resolved KUDU-2268.
-------------------------------
Fix Version/s: 1.7.0
Assignee: Todd Lipcon
Resolution: Fixed
> 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
> Assignee: Todd Lipcon
> Priority: Major
> Fix For: 1.7.0
>
>
> 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)
