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

To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org

Reply via email to