[
https://issues.apache.org/jira/browse/SENTRY-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16311777#comment-16311777
]
kalyan kumar kalvagadda commented on SENTRY-2113:
-------------------------------------------------
[~spena]
As event-id in the notification is not unique, Sentry uses notification hash of
the notification to verify it a notification is processed.
Currently, this has is stored only in MSentryPathChange which is not designed
to store all the notifications fetched from HMS.
This jira is created to have notification has in MSentryHmsNotification, we it
records every notification that is fetched from HMS.
> MSentryHmsNotification should also hold the notification hash
> --------------------------------------------------------------
>
> Key: SENTRY-2113
> URL: https://issues.apache.org/jira/browse/SENTRY-2113
> Project: Sentry
> Issue Type: Bug
> Components: Sentry
> Affects Versions: 2.1.0
> Reporter: kalyan kumar kalvagadda
> Assignee: kalyan kumar kalvagadda
> Attachments: SENTRY-2113.001.patch, SENTRY-2113.002.patch,
> SENTRY-2113.003.patch
>
>
> Currently MSentryHmsNotification is holding notification-id but it should be
> extended to hold the notification hash.
> We are currently using MSentryPathChange to get the notification hash but
> this information is not reliable as MSentryPathChange will store all the
> notifications the HMSFollower gets from HMS. MSentryPathChange will only
> store the notifications that needed to sync HDFS ACL's.
> Unlike MSentryPathChange, MSentryHmsNotification is designed to record the
> information of all the notifications that HMSFollower receives from HMS.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
