[
https://issues.apache.org/jira/browse/SENTRY-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kalyan kumar kalvagadda updated SENTRY-939:
-------------------------------------------
Fix Version/s: (was: 2.0.0)
2.1.0
Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the
fix version if you intend to make it into 2.0.0 release.
> Provide a configuration to be able to fall back to orginal HDFS user:group
> when NN has stale sentry permissions
> ---------------------------------------------------------------------------------------------------------------
>
> Key: SENTRY-939
> URL: https://issues.apache.org/jira/browse/SENTRY-939
> Project: Sentry
> Issue Type: Bug
> Affects Versions: 1.4.0
> Reporter: Sravya Tirukkovalur
> Assignee: Sravya Tirukkovalur
> Fix For: 2.1.0
>
>
> Seems like some sentry users have a batch id for each application which
> creates the directory, ingests the data, then creates a table/partition over
> it. So the batch id is the the original owner of this directory.
> When NN has stale permissions during the time it cannot talk to Sentry (if
> sentry is down), falling back to hive:hive blocks everyone it would be
> helpful if at least this batch id has access otherwise ingest pipelines may
> break during this time. So would be helpful to provide a way to configure
> this behavior.
> - This does not entail ACLS.
> - We should add hive:hive as acl to make sure hive has access
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
