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

Ashish Kumar Singh commented on HIVE-7345:
------------------------------------------

[~navis] Just to make sure we are on the same page, I am stating my 
understandings below.

1. Unable to establish connection:
beeline>!connect jdbc:hive2://localhost:10000
if the connection succeeds:
  0: jdbc:hive2://localhost:10000>
else
  **beeline throws an error message telling the connection failed**
  beeline>

2. Closing an active connection:
0: jdbc:hive2://localhost:10000> Closing: org.apache.hive.jdbc.HiveConnection
beeline>

Are you suggesting in case 1, i.e., Unable to establish connection, we should 
have something like this:
beeline>!connect jdbc:hive2://localhost:10000
if the connection succeeds:
  0: jdbc:hive2://localhost:10000>
else
  **beeline throws an error message telling the connection failed**
  0: jdbc:hive2://abclocalhost:10000 (closed)>

> Beeline changes its prompt to reflect successful database connection even 
> after failing to connect
> --------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-7345
>                 URL: https://issues.apache.org/jira/browse/HIVE-7345
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Ashish Kumar Singh
>            Assignee: Ashish Kumar Singh
>         Attachments: HIVE-7345.patch
>
>
> Beeline changes its prompt to reflect successful database connection even 
> after failing to connect, which is misleading.
> {code}
> [asingh@e1118 tpcds]$ beeline -u "jdbc:hive2://abclocalhost:10000 hive"
> scan complete in 5ms
> Connecting to jdbc:hive2://abclocalhost:10000
> Error: Invalid URL: jdbc:hive2://abclocalhost:10000 (state=08S01,code=0)
> Beeline version 0.12.0-cdh5.1.0-SNAPSHOT by Apache Hive
> 0: jdbc:hive2://abclocalhost:10000> show tables;
> No current connection
> {code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to