sentry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shreepadma Venugopalan (JIRA)" <>
Subject [jira] [Commented] (SENTRY-4) Rename Configuration properties that mention hive but are sentry related
Date Fri, 30 Aug 2013 20:58:52 GMT


Shreepadma Venugopalan commented on SENTRY-4:

[~gchanan]: Thanks for doing this. I think what you are proposing sounds good mostly. Wondering
if hive.sentry.server should be renamed to something more generic or should we add a system
specific variable? Benefit of adding a framework specific variable is the ability to provide
containers for each of the systems. i.e., search and hive can have their own namespaces and
policies. The obvious downside is the inability to share policies between two systems eg.,
impala and hive.
> Rename Configuration properties that mention hive but are sentry related
> ------------------------------------------------------------------------
>                 Key: SENTRY-4
>                 URL:
>             Project: Sentry
>          Issue Type: Improvement
>            Reporter: Gregory Chanan
>            Assignee: Gregory Chanan
> I'm thinking of the following properties, I'll check if there are others:
> hive.sentry.provider -> sentry.provider
> hive.sentry.provider.resource -> sentry.provider.resource
> hive.sentry.server -> sentry.server
> I'm happy to implement this, just need some guidance on what you want to do about compatibility.
> I was thinking the following:
> 1) If only old names used: accept old values, log warning
> 2) If old and new names used: use new values, log warning about old names being ignored
> 3) If only old new names used: use new values, no log warning
> Thoughts?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message