[ https://issues.apache.org/jira/browse/SENTRY-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Na Li updated SENTRY-1854: -------------------------- Attachment: SENTRY-1854.003-sentry-ha-redesign.patch v3. update based on Sasha comments > HMSFollower should handle notifications even if HDFS sync is disabled. > ---------------------------------------------------------------------- > > Key: SENTRY-1854 > URL: https://issues.apache.org/jira/browse/SENTRY-1854 > Project: Sentry > Issue Type: Sub-task > Components: Sentry > Affects Versions: 2.0.0 > Reporter: Na Li > Assignee: Na Li > Fix For: 2.0.0 > > Attachments: SENTRY-1854.001-sentry-ha-redesign.patch, > SENTRY-1854.002-sentry-ha-redesign.patch, > SENTRY-1854.003-sentry-ha-redesign.patch > > > Currently, Sentry does not start HMSFollower when HDFS sync is disabled. This > breaks PERM sync. For example, when a table/database is dropped, its > permission should be removed when perm sync is enabled. Without HMSFollower, > Sentry does not know when table/database is dropped, and therefore, cannot > remove the permission accordingly. > Sentry needs to make updates to have the follow behavior > 1) When HDFS sync is disabled + PERM sync is disabled, do not start > HMSFollower > 2) when HDFS sync is enabled or PERM sync is enabled, start HMSFollower > (Sentry change). > 3) when HDFS sync is enabled, we save path change and perm change. nothing > more. > 4) when perm sync is enabled, we update perm when table/database is created, > dropped or altered, nothing more. -- This message was sent by Atlassian JIRA (v6.4.14#64029)