[
https://issues.apache.org/jira/browse/IMPALA-8572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16930707#comment-16930707
]
ASF subversion and git services commented on IMPALA-8572:
---------------------------------------------------------
Commit d155ef01f5708febf296dd0c2d0db921240bafb1 in impala's branch
refs/heads/master from Bharath Vissapragada
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=d155ef0 ]
IMPALA-8572: Skip test_lineage_output on S3
The test has a hbase dependency that does not run in S3.
Change-Id: I781c2dc42c042747eed6134cea4f3f0879a40294
Reviewed-on: http://gerrit.cloudera.org:8080/14230
Tested-by: Impala Public Jenkins <impala-public-jenk...@cloudera.com>
Reviewed-by: Sahil Takiar <stak...@cloudera.com>
> 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: bharath v
> Priority: Critical
> Fix For: Impala 3.4.0
>
>
> 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
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
