[ https://issues.apache.org/jira/browse/HIVE-16188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924611#comment-15924611 ]
Sahil Takiar commented on HIVE-16188: ------------------------------------- Looks like there are some related test failures: TestJdbcWithMiniHS2.org.apache.hive.jdbc.TestJdbcWithMiniHS2 TestJdbcDriver2.testSetOnConnection Will fix those + will add some new tests. [~pgarg_impala_3a7b] - the fix I am working on may be Hive specific (the fix requires a change to {{HiveSessionImpl}}). From your description it seems you are trying to connect to Impala, correct? I'm not sure how Beeline connects to Impala so I'm not 100% if this change will work for Impala too. > beeline should block the connection if given invalid database name. > ------------------------------------------------------------------- > > Key: HIVE-16188 > URL: https://issues.apache.org/jira/browse/HIVE-16188 > Project: Hive > Issue Type: Bug > Components: Hive > Reporter: Pavas Garg > Assignee: Sahil Takiar > Priority: Minor > Attachments: HIVE-16188.1.patch > > > When using beeline shell to connect to HS2 or impalaD as below - > beeline -u > "jdbc:hive2://impalad-host-name.com:21050/XXX;principal=impala/impalad-host-name....@domain.example.com" > > Providing a invalid database name as XXX - the connection is made. > It should ideally stop the connection to be successfull. > Even though, the beeline tool does not allow to move forward, unless you > provide a valid DB name, like > Use <Database-Name>; -- This message was sent by Atlassian JIRA (v6.3.15#6346)