[
https://issues.apache.org/jira/browse/HIVE-16188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924561#comment-15924561
]
Vihang Karajgaonkar commented on HIVE-16188:
--------------------------------------------
Hi [~stakiar] Thanks for the patch. Does this change the behavior with HiveCLI
too? Also, would be good if we can add a test case for this.
> 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)
