[
https://issues.apache.org/jira/browse/SENTRY-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Hao updated SENTRY-1605:
----------------------------
Resolution: Fixed
Fix Version/s: 1.8.0
Status: Resolved (was: Patch Available)
> 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
> Affects Versions: 1.8.0
> Reporter: Vadim Spector
> Assignee: Vadim Spector
> Fix For: 1.8.0
>
> 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)
