You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sentry.apache.org by "Gregory Chanan (JIRA)" <ji...@apache.org> on 2013/09/17 02:26:52 UTC
[jira] [Updated] (SENTRY-4) Rename Configuration properties that
mention hive but are sentry related
[ https://issues.apache.org/jira/browse/SENTRY-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gregory Chanan updated SENTRY-4:
--------------------------------
Attachment: SENTRY-4.patch
* Attached SENTRY-4.patch *
Here is a patch that implements my proposal above.
> Rename Configuration properties that mention hive but are sentry related
> ------------------------------------------------------------------------
>
> Key: SENTRY-4
> URL: https://issues.apache.org/jira/browse/SENTRY-4
> Project: Sentry
> Issue Type: Improvement
> Reporter: Gregory Chanan
> Assignee: Gregory Chanan
> Attachments: SENTRY-4.patch
>
>
> 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: http://www.atlassian.com/software/jira