You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Sushanth Sowmyan (JIRA)" <ji...@apache.org> on 2016/05/07 19:31:12 UTC
[jira] [Updated] (HIVE-13670) Improve Beeline connect/reconnect
semantics
[ https://issues.apache.org/jira/browse/HIVE-13670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sushanth Sowmyan updated HIVE-13670:
------------------------------------
Summary: Improve Beeline connect/reconnect semantics (was: Improve Beeline reconnect semantics)
> Improve Beeline connect/reconnect semantics
> -------------------------------------------
>
> Key: HIVE-13670
> URL: https://issues.apache.org/jira/browse/HIVE-13670
> Project: Hive
> Issue Type: Improvement
> Affects Versions: 2.1.0
> Reporter: Sushanth Sowmyan
> Assignee: Sushanth Sowmyan
> Attachments: HIVE-13670.2.patch, HIVE-13670.3.patch, HIVE-13670.patch
>
>
> For most users of beeline, chances are that they will be using it with a single HS2 instance most of the time. In this scenario, having them type out a jdbc uri for HS2 every single time to !connect can get tiresome. Thus, we should improve semantics so that if a user does a successful !connect, then we must store the last-connected-to-url, so that if they do a !close, and then a !reconnect, then !reconnect should attempt to connect to the last successfully used url.
> Also, if they then do a !save, then that last-successfully-used url must be saved, so that in subsequent sessions, they can simply do !reconnect rather than specifying a url for !connect.
> In addition, it would be useful to introduce a new way of doing !connect that does involve typing out a jdbc url every time (since this is highly likely to be error-prone)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)