You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Laszlo Bodor (JIRA)" <ji...@apache.org> on 2018/07/24 15:53:00 UTC
[jira] [Assigned] (HIVE-20229) Improve beeline to show exception
backtrace on connection failure
[ https://issues.apache.org/jira/browse/HIVE-20229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Laszlo Bodor reassigned HIVE-20229:
-----------------------------------
Assignee: Laszlo Bodor
> Improve beeline to show exception backtrace on connection failure
> -----------------------------------------------------------------
>
> Key: HIVE-20229
> URL: https://issues.apache.org/jira/browse/HIVE-20229
> Project: Hive
> Issue Type: Bug
> Components: Beeline
> Reporter: Zoltan Haindrich
> Assignee: Laszlo Bodor
> Priority: Major
>
> Currently there are cases when beeline could print out pretty non informative error messages...
> like:
> {code}
> java.sql.SQLException: Could not open client transport with JDBC Uri: jdbc:hive2://xxx:10000: null
> {code}
> which is okay most of the time; but I think we would need to add some --debug or something which sends the stacktrace also...because it's very hard to start troubleshooting a "null" message
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)