[
https://issues.apache.org/jira/browse/SENTRY-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16316613#comment-16316613
]
Hadoop QA commented on SENTRY-2113:
-----------------------------------
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12905109/SENTRY-2113.005.patch
against master.
{color:green}Overall:{color} +1 all checks pass
{color:green}SUCCESS:{color} all tests passed
Console output:
https://builds.apache.org/job/PreCommit-SENTRY-Build/3611/console
This message is automatically generated.
> 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, SENTRY-2113.005.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)
