[
https://issues.apache.org/jira/browse/HIVE-28713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sai Hemanth Gantasala reassigned HIVE-28713:
--------------------------------------------
Assignee: Sai Hemanth Gantasala
> 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)
