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

ASF GitHub Bot commented on HIVE-15858:
---------------------------------------

GitHub user sankarh opened a pull request:

    https://github.com/apache/hive/pull/144

    HIVE-15858: Beeline ^C doesn't close the session

    HIVE-15858: Beeline ^C doesn't close the session
    Fixed by closing the sessions through ShutdownHook.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/sankarh/hive HIVE-15858

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/hive/pull/144.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #144
    
----
commit 07624a9328f9f8256aeb2f10a22058f4cf1aa693
Author: Sankar Hariappan <mailtosank...@gmail.com>
Date:   2017-02-09T10:29:23Z

    HIVE-15858: Beeline ^C doesn't close the session

----


> Beeline ^C doesn't close the session
> ------------------------------------
>
>                 Key: HIVE-15858
>                 URL: https://issues.apache.org/jira/browse/HIVE-15858
>             Project: Hive
>          Issue Type: Bug
>          Components: Beeline
>            Reporter: Sankar Hariappan
>            Assignee: Sankar Hariappan
>         Attachments: HIVE-15858.01.patch
>
>
> When open multiple connections through Beeline to Hiveserver2 and if tries to 
> close the client using !quit or ^C command, it looks like all the 
> connections/sessions are not getting closed.
> !quit seems to close the current active connection but fails to close other 
> open sessions.
> ^C doesn't close any session.
> This behaviour is noticed only with the HTTP mode of transport 
> (hive.server2.transport.mode=http). In case of BINARY mode, server triggers 
> the close session when a tcp connection is closed by peer.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to