You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Sergey Shelukhin (JIRA)" <ji...@apache.org> on 2017/08/16 02:40:00 UTC

[jira] [Updated] (HIVE-17330) refactor TezSessionPoolManager to separate its multiple functions

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

Sergey Shelukhin updated HIVE-17330:
------------------------------------
    Attachment: HIVE-17330.patch

This mostly moves code (see JIRA description). One open question remaining is whether openSessions and closeAll... should also be moved into the pool from the manager. It looks like existing code only adds pool session to openSessions, and not custom user sessions. That might be a bug introduces with one of the previous changes, as the intent (e.g. closeIfNotDefault) seems to be for openSessions to contain both pool and non-pool sessions. If the latter is the case I'll also fix it here, will dig into the history tomorrow.

cc [~sseth]

> refactor TezSessionPoolManager to separate its multiple functions
> -----------------------------------------------------------------
>
>                 Key: HIVE-17330
>                 URL: https://issues.apache.org/jira/browse/HIVE-17330
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Sergey Shelukhin
>         Attachments: HIVE-17330.patch
>
>
> TezSessionPoolManager would retain things specific to current Hive session management. 
> The session pool itself, as well as expiration tracking, the pool session implementation, and some config validation can be separated out and made independent from the pool.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)