[
https://issues.apache.org/jira/browse/SENTRY-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15988960#comment-15988960
]
kalyan kumar kalvagadda commented on SENTRY-1726:
-------------------------------------------------
HMS follower periodically pulls new notifications from the HMS. It needs to
know the last notification id that sentry processed in order to send a request
to HMS asking for latest notifications.
Currently HMS follower is depending on the notification stores in
SENTRY_PATH_CHANGE table. This may not give the last notification processed all
the time.
Let's take en example here
||Notification ID || Event || MAX(Notification ID) in SENTRY_PATH_CHANGE||
|100| create table db1.tb1 | 100
|101| drop table db1.tb1 | 99
After processing notification with ID 101 in above example, MAX(Notification
ID) in SENTRY_PATH_CHANGE would give you 99. If HMS follower depends on this
information, it has to process notifications 100 and 101 again. This is not we
want.
*Solution:*
Store Last Notification ID in separate table and use it instead.
> sql changes to store last notification-id processed
> ---------------------------------------------------
>
> Key: SENTRY-1726
> URL: https://issues.apache.org/jira/browse/SENTRY-1726
> Project: Sentry
> Issue Type: Improvement
> Components: Sentry
> Affects Versions: sentry-ha-redesign
> Reporter: kalyan kumar kalvagadda
> Assignee: kalyan kumar kalvagadda
> Fix For: sentry-ha-redesign
>
> Attachments: SENTRY-1726.001-sentry-ha-redesign.patch,
> SENTRY-1726.002-sentry-ha-redesign.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
