You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Sai Hemanth Gantasala (Jira)" <ji...@apache.org> on 2025/01/31 14:58:00 UTC
[jira] [Commented] (HIVE-28713) Add source fields for NOTIFICATION_LOG table
[ https://issues.apache.org/jira/browse/HIVE-28713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17922733#comment-17922733 ]
Sai Hemanth Gantasala commented on HIVE-28713:
----------------------------------------------
I'm inclined to include this in an 'environment_context' variable in the notification message as we get two benefits. 1) inter-operability remains intact 2) In the environment_context variable, we can store some fields like engine, Impala's catalog_service_id, Impala's catalog_service_version, and incremental stats (which are Impala specific and these are currently stored in table_properties).
> Add source fields for NOTIFICATION_LOG table
> --------------------------------------------
>
> Key: HIVE-28713
> URL: https://issues.apache.org/jira/browse/HIVE-28713
> Project: Hive
> Issue Type: New Feature
> Reporter: Quanlong Huang
> Assignee: Sai Hemanth Gantasala
> Priority: Major
>
> HMS event consumers like Impala will also generate HMS events in HMS operations. They would like to skip processing such self-generated events. However, currently in the NOTIFICATION_LOG table, there are no fields to identify where the event comes from.
> {noformat}
> Table "public.NOTIFICATION_LOG"
> Column | Type | Collation | Nullable | Default
> ----------------+------------------------+-----------+----------+---------
> NL_ID | bigint | | not null |
> EVENT_ID | bigint | | not null |
> EVENT_TIME | integer | | not null |
> EVENT_TYPE | character varying(32) | | not null |
> CAT_NAME | character varying(256) | | |
> DB_NAME | character varying(128) | | |
> TBL_NAME | character varying(256) | | |
> MESSAGE | text | | |
> MESSAGE_FORMAT | character varying(16) | | |{noformat}
> Fields like client address, client id (customized) will be helpful. HMS clients can set their client id, e.g. Impala's catalog_service_id, when calling HMS RPCs.
> CC [~hemanth619] , [~VenuReddy] , [~ngangam] , [~amansinha]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)