Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
Currently there are cases when beeline could print out pretty non informative error messages...
like:
java.sql.SQLException: Could not open client transport with JDBC Uri: jdbc:hive2://xxx:10000: null
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