[
https://issues.apache.org/jira/browse/HIVE-16188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928951#comment-15928951
]
Vihang Karajgaonkar commented on HIVE-16188:
--------------------------------------------
I looked into code again and I think client side is better place to handle this
validation than on the HiveServer2 side. In addition to this check in
HiveSession I think we should also add this check in
HiveDriver:parseURLforPropertyInfo() method. Since we know that connection
request will fail there is no need to even attempt making a connection. What do
you think [~stakiar]?
> 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, HIVE-16188.2.patch
>
>
> When using beeline shell to connect to HS2 or impalaD as below -
> Connection to HS2 using beeline tool on port 10000 -
> beeline -u
> "jdbc:hive2://HS2-host-name:10000/default;principal=hive/hs2-host-n...@domain.example.com"
> Connection to ImpalaD using beeline tool on port 21050 -
> 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)
