[
https://issues.apache.org/jira/browse/SENTRY-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15755228#comment-15755228
]
Aihua Xu commented on SENTRY-1570:
----------------------------------
[~hahao], [~vspector] FYI.
I'm investigating such issues from Hive and would like to improve this on the
Sentry side. Can you guys foresee if there is any issue with that approach?
Currently every time when it happened, it will be P1 issue for Hive and Sentry.
> One task failure in MetastoreCacheInitializer should not cause HMS not to
> start
> -------------------------------------------------------------------------------
>
> Key: SENTRY-1570
> URL: https://issues.apache.org/jira/browse/SENTRY-1570
> Project: Sentry
> Issue Type: Improvement
> Components: Hive Plugin
> Affects Versions: 1.5.1
> Reporter: Aihua Xu
>
> Seems it's common that HMS metastore may have incorrect metadata for one or
> more databases/tables/partitions due to various reasons (see SENTRY-1564).
> Right now, HMS will not start properly if MetastoreCacheInitializer fails to
> initialize authzPath and the whole Hive service becomes unusable.
> Propose to continue the cache initialization even there is a task failure.
> The databases/tables with the issues will be unusable until the authzPath
> cache for them is built.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
