[jira] [Commented] (SENTRY-2114) Fix behavior of HMSFollower when HDFS sync is not enabled

["Na Li (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SENTRY-2114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16310249#comment-16310249 ] 

Na Li commented on SENTRY-2114:
-------------------------------

The default value of sentry last notification ID should be 0. So the step 1 and step 2 can be combined into a single step "fetch and process new notifications > sentry last processed notification ID"

> 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)