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

["Stamatis Zampetakis (Jira)" <ji...@apache.org>]

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

Stamatis Zampetakis resolved HIVE-26095.
----------------------------------------
    Resolution: Won't Fix

As discussed under the [PR|https://github.com/apache/hive/pull/3156#discussion_r840394149] it is possible to obtain the query id via the Hive configuration (using {{hive.query.id}} property) so there is no need to introduce a new API for this purpose thus I am closing this JIRA as won't fix.

> 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
>          Time Spent: 2h 20m
>  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.7#820007)