[
https://issues.apache.org/jira/browse/HIVE-16188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15923679#comment-15923679
]
Sahil Takiar commented on HIVE-16188:
-------------------------------------
[~pgarg_impala_3a7b] I took a look at this today and think I have a fix.
Assigning this to myself, let me know if you have any objections.
Attaching a patch with initial approach to see what Hive QA thinks.
> 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
>
> When using beeline shell to connect to HS2 or impalaD as below -
> beeline -u
> "jdbc:hive2://impalad-host-name.com:21050/XXX;principal=impala/[email protected]"
>
> 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)
