You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Fredy Wijaya (JIRA)" <ji...@apache.org> on 2019/06/21 05:24:01 UTC
[jira] [Resolved] (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:all-tabpanel ]
Fredy Wijaya resolved IMPALA-8443.
----------------------------------
Resolution: Fixed
Fix Version/s: Impala 3.3.0
> 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
> Fix For: Impala 3.3.0
>
>
> 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)