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 "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/06/21 04:36:00 UTC
[jira] [Commented] (IMPALA-8443) Record time spent in authorization
in the runtime profile
[ https://issues.apache.org/jira/browse/IMPALA-8443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16869175#comment-16869175 ]
ASF subversion and git services commented on IMPALA-8443:
---------------------------------------------------------
Commit 65175a23b2ed73d91734607d474ba80e15323c9b in impala's branch refs/heads/master from Tamas Mate
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=65175a2 ]
IMPALA-8443: Record time spent in authorization in the runtime profile
The analysis and authorization is handled together as authorization
depends on the results of the analysis. The timeline EventSequence is
moved into the AuthorizationContext and the markEvent is called during
the postAuthorize method.
In some cases the EventSequence is not available when the
AuthorizationContext is created therefore it is wrapped in Optional.
Change-Id: I5bb85e57fcc75d41f3eb2911e6d375e0da6f82ae
Reviewed-on: http://gerrit.cloudera.org:8080/13353
Reviewed-by: Impala Public Jenkins <im...@cloudera.com>
Tested-by: Impala Public Jenkins <im...@cloudera.com>
> Record time spent in authorization in the runtime profile
> ---------------------------------------------------------
>
> Key: IMPALA-8443
> URL: https://issues.apache.org/jira/browse/IMPALA-8443
> Project: IMPALA
> Issue Type: Improvement
> Components: Frontend
> Affects Versions: Impala 3.2.0
> Reporter: bharath v
> Assignee: Tamas Mate
> Priority: Major
> Labels: newbie, supportability
>
> Authorization is done as a part of analysis. It helps to have the time spent in authorization recorded as a part of the query profile timeline. Something like as follows. Helps to debug issues when bottleneck is in authorization.
> {noformat}
> Query Compilation
> Metadata load started: 4ms (4559114)
> Metadata load finished. loaded-tables=1/2 load-requests=1 catalog-updates=3: 2.60s (2599515306)
> Authorization finished (Ranger|Sentry): xxxxx ++++++++++
> Analysis finished: 1.9m (113860685080)
> Value transfer graph computed: 1.9m (113863830763)
> Single node plan created: 1.9m (116880551103)
> Runtime filters computed: 1.9m (116880914428)
> Distributed plan created: 1.9m (116882951541)
> Lineage info computed: 1.9m (116884735701)
> Planning finished: 1.9m (116900204008)
> Planning finished: 1.9m (116900208344)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org