You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Dinesh Garg (JIRA)" <ji...@apache.org> on 2019/08/16 00:17:00 UTC
[jira] [Updated] (IMPALA-8572) Move query hook execution to before
query unregistration
[ https://issues.apache.org/jira/browse/IMPALA-8572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dinesh Garg updated IMPALA-8572:
--------------------------------
Priority: Critical (was: Major)
> Move query hook execution to before query unregistration
> --------------------------------------------------------
>
> Key: IMPALA-8572
> URL: https://issues.apache.org/jira/browse/IMPALA-8572
> Project: IMPALA
> Issue Type: Sub-task
> Components: Backend
> Reporter: radford nguyen
> Assignee: radford nguyen
> Priority: Critical
>
> The backend currently executes query event hooks during {{ImpalaServer::UnregisterQuery}}, which may actually only happen a long time after the query has actually executed. We depend on either the client closing the query/session, the client's connection dropping, or an idle session timing out.
> e.g. the following sequence is possible.
> # User executes query from Hue.
> # User goes home for weekend, leaving Hue tab open in browser
> # If we're lucky, the session timeout expires after some amount of idle time.
> # The query gets unregistered, hooks get executed
> It would generally be desirable to move the lineage logger earlier in the query lifecycle, so it occurs as soon as all of the required data is available.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org