hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavas Garg (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (HIVE-16188) beeline should block the connection if given invalid database name.
Date Tue, 14 Mar 2017 17:56:41 GMT

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

Pavas Garg edited comment on HIVE-16188 at 3/14/17 5:56 PM:
------------------------------------------------------------

1. I don't think you can specify/select the database to start the connection with Hive CLI.
2. Hive CLI is deprecated, use beeline shell going forward.



was (Author: pavasgarg):
1. I don't think you can specify/select the database to start the connection with.
2. Hive CLI is deprecated, use beeline shell going forward.


> 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.com@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)

Mime
View raw message