[
https://issues.apache.org/jira/browse/SENTRY-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vadim Spector updated SENTRY-1605:
----------------------------------
Description: 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. (was: 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 and 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. )
> 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
>
> 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.4#6332)
