You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Zoltán Borók-Nagy (JIRA)" <ji...@apache.org> on 2018/01/11 11:04:00 UTC

[jira] [Closed] (IMPALA-2248) Make idle_session_timeout a query option

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

Zoltán Borók-Nagy closed IMPALA-2248.
-------------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: Impala 2.5.0)
                   Impala 2.12.0

Fixed in https://github.com/apache/impala/commit/ce65b43d47d16840998eb5fab5333695050ac436


> Make idle_session_timeout a query option
> ----------------------------------------
>
>                 Key: IMPALA-2248
>                 URL: https://issues.apache.org/jira/browse/IMPALA-2248
>             Project: IMPALA
>          Issue Type: New Feature
>    Affects Versions: Impala 2.0
>            Reporter: Matthew Jacobs
>            Assignee: Zoltán Borók-Nagy
>              Labels: query-lifecycle, ramp-up
>             Fix For: Impala 2.12.0
>
>
> We currently have a process-wide session timeout (see --idle_session_timeout), but it would be useful to also have the ability to set per-session timeouts. We can do this by taking a parameter in the HS2 OpenSession() call (it already has a map of properties) and changing the session timeout logic in impala-server.cc.
> This could be set to a lower value by some clients, e.g. Hue, that do not close queries automatically and want to ensure queries aren't left open for a long time without requiring that all clients have the same session timeout.



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