[jira] [Updated] (SENTRY-2115) Sentry will be out of sync with HMS on disabling and enabling HDFS synchronization.

["kalyan kumar kalvagadda (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SENTRY-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

kalyan kumar kalvagadda updated SENTRY-2115:
--------------------------------------------
    Description: 
On disabling HDFS sync, HMSFollower would update the SENTRY_HMS_NOTIFICATION_ID table but not the MSentryPathChange table.

When  HDFS sync is enabled again, HMSFollower would continue fetching new notifications and process them and update the MSentryPathChange and MAuthzPathsMapping info. This is not correct. 

  was:
On disabling HDFS sync, HMSFollower would update the SENTRY_HMS_NOTIFICATION_ID table but not the MSentryPathChange table.

When  HDFS sync is enabled again, notification information in SENTRY_HMS_NOTIFICATION_ID  ahead of information in MSentryPathChange. If HMSFollower follows the current logic it will notifications that are fetched when the feature was turned off.


> Sentry will be out of sync with HMS on disabling and enabling HDFS synchronization.
> -----------------------------------------------------------------------------------
>
>                 Key: SENTRY-2115
>                 URL: https://issues.apache.org/jira/browse/SENTRY-2115
>             Project: Sentry
>          Issue Type: Bug
>            Reporter: kalyan kumar kalvagadda
>            Assignee: kalyan kumar kalvagadda
>
> On disabling HDFS sync, HMSFollower would update the SENTRY_HMS_NOTIFICATION_ID table but not the MSentryPathChange table.
> When  HDFS sync is enabled again, HMSFollower would continue fetching new notifications and process them and update the MSentryPathChange and MAuthzPathsMapping info. This is not correct. 



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