You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/03/30 17:09:00 UTC

[jira] [Updated] (HIVE-26095) Add queryid in QueryLifeTimeHookContext

     [ https://issues.apache.org/jira/browse/HIVE-26095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated HIVE-26095:
----------------------------------
    Labels: pull-request-available  (was: )

> Add queryid in QueryLifeTimeHookContext
> ---------------------------------------
>
>                 Key: HIVE-26095
>                 URL: https://issues.apache.org/jira/browse/HIVE-26095
>             Project: Hive
>          Issue Type: New Feature
>          Components: Hooks
>            Reporter: Stamatis Zampetakis
>            Assignee: Stamatis Zampetakis
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 4.0.0-alpha-2
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> A [QueryLifeTimeHook|https://github.com/apache/hive/blob/6c0b86ef0cfc67c5acb3468408e1d46fa6ef8024/ql/src/java/org/apache/hadoop/hive/ql/hooks/QueryLifeTimeHook.java] is executed various times in the life-cycle of a query but it is not always possible to obtain the id of the query. The query id is inside the {{HookContext}} but the latter is not always available notably during compilation.
> The query id is useful for many purposes as it is the only way to uniquely identify the query/command that is currently running. It is also the only way to match together events appearing in before and after methods.
> The goal of this jira is to add the query id in [QueryLifeTimeHookContext|https://github.com/apache/hive/blob/6c0b86ef0cfc67c5acb3468408e1d46fa6ef8024/ql/src/java/org/apache/hadoop/hive/ql/hooks/QueryLifeTimeHookContext.java] and make it available during all life-cycle events.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)