[jira] [Commented] (SENTRY-1605) SENTRY-1508 need to be fixed because of Kerberos initialization issue

["Vadim Spector (JIRA)" <ji...@apache.org>]

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

Vadim Spector commented on SENTRY-1605:
---------------------------------------

Patch 002:

1. better javadoc per Hao's review
2. explicit logic making first full update mandatory, regardless of the sequence numbers on Sentry vs MetastorePlugin. Although the implementations make sure to assign the initial numbers to different constants, it is brittle and can be broken.

> SENTRY-1508 need to be fixed because of Kerberos initialization issue
> ---------------------------------------------------------------------
>
>                 Key: SENTRY-1605
>                 URL: https://issues.apache.org/jira/browse/SENTRY-1605
>             Project: Sentry
>          Issue Type: Bug
>            Reporter: Vadim Spector
>            Assignee: Vadim Spector
>         Attachments: SENTRY-1605.001.patch, SENTRY-1605.002.patch
>
>
> SENTRY-1508 performs full Sentry HDFS sync at the construction time. Turns out, it does not work with Kerberos on, because the Hive code initialized Kerberos client only AFTER instantiating MetastorePlugin. Fix is pretty straightforward: MetastorePlugin should not attempt synchronization with Sentry from the constructor. It should rely on the housekeeping thread's SyncTask to ultimately succeed in pushing the first full update. The subtle point is that until it happens, all partial updates going through MetastorePlugin should skip Sentry notification step while keeping updating the MetastorePlugin's local cache as usual. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)