hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sushanth Sowmyan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-13670) Improve Beeline reconnect semantics
Date Thu, 05 May 2016 22:13:12 GMT

     [ https://issues.apache.org/jira/browse/HIVE-13670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sushanth Sowmyan updated HIVE-13670:
------------------------------------
    Status: Open  (was: Patch Available)

Canceling patch for now - Given that we already have a "read-only" set of variables as specified
by --hivevar, introducing a notion of saved-vars seems like a big feature by itself to implement
this. Possibly a good idea nevertheless to have a separate jira to introduce a notion of saved-vars,
but not as a side-effect of needing to simplify connection semantics.

Also, while this improves usability from a end-user perspective, it might be good for a cluster
admin to define these and have these be available across the board so that end users only
pick a "cluster name" and use it, rather than defining it themselves, and then !save-ing it.

> Improve Beeline 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.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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message