You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@sentry.apache.org by "kalyan kumar kalvagadda (JIRA)" <ji...@apache.org> on 2018/01/02 16:45:00 UTC

[jira] [Created] (SENTRY-2113) MSentryHmsNotification should also hold the notification hash

kalyan kumar kalvagadda created SENTRY-2113:
-----------------------------------------------

             Summary: 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


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 theat HMSFollower receives from HMS.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)