[
https://issues.apache.org/jira/browse/SENTRY-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13768535#comment-13768535
]
Gregory Chanan commented on SENTRY-4:
-------------------------------------
With SENTRY-14 in mind, this is what I think should change in
HiveAuthzConf.java:
OLD NEW
hive.sentry.provider => sentry.provider
hive.sentry.provider.resource => sentry.hive.provider.resource
hive.sentry.server => sentry.hive.server
hive.sentry.restrict.defaultDB => sentry.hive.restrict.defaultDB
hive.sentry.testing.mode => sentry.hive.testing.mode
hive.sentry.udf.whitelist => sentry.hive.udf.whitelist
hive.sentry.allow.hive.impersonation =>
sentry.hive.allow.hive.impersonation
hive.sentry.failure.hooks => sentry.hive.failure.hooks
Let me know if there are any objections.
> 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
>
> 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
