hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carl Steinbach (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-11485) Session close should not close async SQL operations
Date Sun, 03 Apr 2016 23:11:25 GMT

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

Carl Steinbach commented on HIVE-11485:
---------------------------------------

bq. Sure. whats the story from Hive if the client crashes ?

One of the original design goals of HiveServer2 was to provide *logical* sessions that are
completely independent of physical details, including connections and server-side threads
(both of which were problems with HiveServer1). In the future this logical decoupling will
hopefully make it easier to support features like transparent session migration from one HS2
instance to another.

bq. After HIVE-9601, we are seeing the issue is prominent.

HIVE-9601 created a binding between logical sessions and the underlying physical connection.
This violates the design principal I described above and should either be reverted or made
optional.

bq. But, queries running are actually available across sessions and they are not tied to a
session (expect the launch - which requires configuration and resources). And it allows getting
the status of the query across sessions.

No, this is not true. Every Operation is explicitly tied to exactly one logical session. Please
review the Thrift CLIService IDL file for more details.

bq. But session close of the session ( on which operation is launched) closes all the operations
as well.

This is a fundamental principal of the HS2 design. Changing this will screw up a lot of things.
Please don't do this.

> Session close should not close async SQL operations
> ---------------------------------------------------
>
>                 Key: HIVE-11485
>                 URL: https://issues.apache.org/jira/browse/HIVE-11485
>             Project: Hive
>          Issue Type: Improvement
>          Components: HiveServer2
>            Reporter: Amareshwari Sriramadasu
>            Assignee: Deepak Barr
>         Attachments: HIVE-11485.master.patch
>
>
> Right now, session close on HiveServer closes all operations. But, queries running are
actually available across sessions and they are not tied to a session (expect the launch -
which requires configuration and resources). And it allows getting the status of the query
across sessions.
> But session close of the session ( on which operation is launched) closes all the operations
as well. 
> So, we should avoid closing all operations upon closing a session.



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

Mime
View raw message