[
https://issues.apache.org/jira/browse/SENTRY-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16311565#comment-16311565
]
Sergio Peña commented on SENTRY-2113:
-------------------------------------
What is the benefit of keeping it on MSentryHmsNotification? From what I
understand, the hash is used on MSentryPathChange only to avoid writing a
duplicated notification.
> 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
>
>
> 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)
