[
https://issues.apache.org/jira/browse/HIVE-28146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17934058#comment-17934058
]
Quanlong Huang commented on HIVE-28146:
---------------------------------------
The eventTypeSkipList is long if the client just wants one type of events:
[https://github.com/apache/hive/blob/183f8cb41d3dbed961ffd27999876468ff06690c/standalone-metastore/metastore-server/src/main/java/org/apache/hadoop/hive/metastore/messaging/EventMessage.java#L33-L77]
Another pain point is client codes need to be updated whenever there are new
event types introduced in HMS.
It'd be helpful to prioritize this.
> Add positive event type filter to the HMS notification fetch API
> ----------------------------------------------------------------
>
> Key: HIVE-28146
> URL: https://issues.apache.org/jira/browse/HIVE-28146
> Project: Hive
> Issue Type: New Feature
> Reporter: Quanlong Huang
> Assignee: Sai Hemanth Gantasala
> Priority: Major
>
> The current notification fetch API supports filtering on event types:
> {code:java}
> struct NotificationEventRequest {
> 1: required i64 lastEvent,
> 2: optional i32 maxEvents,
> 3: optional list<string> eventTypeSkipList,
> }
> NotificationEventResponse get_next_notification(1:NotificationEventRequest
> rqst){code}
> There are clients like Impala that want to fetch all CREATE_TABLE events on a
> table. It's inconvenient to specify all the other types in the
> 'eventTypeSkipList'. Providing a positive type list like 'eventTypeList'
> would be useful.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
