You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@sentry.apache.org by "Sergio Peña (JIRA)" <ji...@apache.org> on 2018/12/03 15:59:00 UTC
[jira] [Commented] (SENTRY-2468) Replicate owner privileges.
[ https://issues.apache.org/jira/browse/SENTRY-2468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16707415#comment-16707415 ]
Sergio Peña commented on SENTRY-2468:
-------------------------------------
How will you provide this input? Just making sure we have a generic parameter for future privileges that should not be exported/imported either.
> Replicate owner privileges.
> ---------------------------
>
> Key: SENTRY-2468
> URL: https://issues.apache.org/jira/browse/SENTRY-2468
> Project: Sentry
> Issue Type: Sub-task
> Components: Sentry
> Affects Versions: 2.2.0
> Reporter: kalyan kumar kalvagadda
> Assignee: kalyan kumar kalvagadda
> Priority: Major
>
> In general exporting owner privileges is an unnecessary overhead for couple of reasons
> # Owner privileges are updated automatically in the target cluster when Hive replication is performed on the target cluster.
> # Number of owner privileges could be huge and the magnitude of that would increase with increase in the number of databases and tables.
>
> There are still some use cases where there is a need to replicate owner privilege as well. Here are some of them
> # When sentry is not configured in the target cluster when owner privileges feature is enabled in source cluster.
> # When owner privileges feature is enabled in source cluster and not in target cluster.
> In both the above case, target cluster will not have owner privileges for the hive objects that are replicated.
>
> In summary, replicating owner privilege should be configurable.It is better to have it as an input from the administrator performing the export/import operations.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)