[
https://issues.apache.org/jira/browse/HIVE-16188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15944246#comment-15944246
]
Lefty Leverenz commented on HIVE-16188:
---------------------------------------
[~spena], the current plan is for master to become release 3.0.0 so this
issue's fix version should be 3.0.0 instead of 2.2.0.
* [About next 2.3 release |
http://mail-archives.apache.org/mod_mbox/hive-dev/201703.mbox/%3ccams4yue4wn3zabeet-acn6smhup0k8ffgeu3w6m4y9wgjfs...@mail.gmail.com%3e]
Please commit to branch-2 if you want this patch in 2.3.0, which is what we
thought would be 2.2.0 but now that's going to be a special case:
* [Re: Backward incompatible changes |
http://mail-archives.apache.org/mod_mbox/hive-dev/201703.mbox/%3cCAHfHakEL-+C=q5rnrunxfcmqabnpm5m_h6qrokcrns24cv2...@mail.gmail.com%3e]
> 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
> Fix For: 2.2.0
>
> 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/[email protected]"
> Connection to ImpalaD using beeline tool on port 21050 -
> 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)
