[
https://issues.apache.org/jira/browse/SENTRY-2114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16310252#comment-16310252
]
Na Li commented on SENTRY-2114:
-------------------------------
How to handle the following case correctly?
1. HDFS is disabled
2. HDFS is enabled after some time.
The notification indicates many notifications are processed, but they are not
in the change log. A full snapshot should be obtained.
I suggest to get all scenarios analyzed, decide the behavior that work
correctly in all scenarios, and then implement the approach in each scenario.
Without this coordination, we can fix one issue and then creating another issue.
> Fix behavior of HMSFollower when HDFS sync is not enabled
> ---------------------------------------------------------
>
> Key: SENTRY-2114
> URL: https://issues.apache.org/jira/browse/SENTRY-2114
> Project: Sentry
> Issue Type: Bug
> Components: Sentry
> Affects Versions: 2.1.0
> Reporter: kalyan kumar kalvagadda
> Assignee: kalyan kumar kalvagadda
>
> Currently behavior of HMSFollower when HDFS sync disabled is as below.
> # Take full snapshot of HMS
> # Take the Notification Id from the snapshot created.
> # Persist the notification Id to SENTRY_HMS_NOTIFICATION_ID table
> # Fetches notifications and process new notifications after that point.
> *This doesn't make sense. Ideally, I think it should work as below.*
> # Initially, fetch all the notifications with even-id > 0 and process them.
> # Subsequently fetch and process new notifications.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
