[
https://issues.apache.org/jira/browse/HIVE-11485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15092011#comment-15092011
]
Xuefu Zhang commented on HIVE-11485:
------------------------------------
Users may not have any idea of asyc execution, such as those of Hue. It's way
easy to leave those operations behind, consuming HS2 and cluster resources. Not
to mention that they don't even have a way to cancel unwanted running
operations.
Nothing prevents a user session from running days or as long as the operation
takes.
Async execution was introduced as a problematic feature. It was a mistake in my
opinion. As I can see, this is to extend along that route. Before I see a clear
design and benefit, I'd -1 on 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)
