[IMPALA-8443] Record time spent in authorization in the runtime profile

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Impala 3.2.0
• Fix Version/s: Impala 3.3.0
• Component/s: Frontend
• Labels: newbie supportability
• Epic Link: Improve Impala Profile User Experience
• Epic Color: ghx-label-6
• Assignee: Tamas Mate
• Reporter: Bharath Vissapragada
• Created: 21/Apr/19 19:05
• Updated: 05/Feb/24 07:52
• Resolved: 21/Jun/19 05:23

Description

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.

  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)

Issue Links

• causes: IMPALA-11406 Incorrect duration logged in "Authorization check took n ms"
• causes: IMPALA-8750 TestObservability.test_query_profile_contains_query_compilation_events failing when compilation events appear dynamically
• is duplicated by: IMPALA-5353 Add timeline metric for authorization/security checks