[
https://issues.apache.org/jira/browse/SENTRY-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14073936#comment-14073936
]
guoquanshen commented on SENTRY-362:
------------------------------------
hi [~gchanan]
<--Why did SolrAuthzConf change from super(false) to super(true)
if the core-site.xml or core-default.xml in the solr service classpath, then
the solrAuthConf will automatically load it and the user doesn't need to set
solr.hdfs.confdir parameter, I see the HiveAuthConf class alse use the
configutation(true). so , i want to keep consistently with it.
<--getAuthProvider(Configuration authzConf) takes an authzConf, but doesn't
really use it
yeah, I will remove the parameter.
> When sentry integrate into solr, the create instance of backend needs
> configure parameters from solrAuthzConf not hadoopConf
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: SENTRY-362
> URL: https://issues.apache.org/jira/browse/SENTRY-362
> Project: Sentry
> Issue Type: Bug
> Affects Versions: 1.3.0
> Reporter: guoquanshen
> Assignee: guoquanshen
> Attachments: SENTRY-362.patch, SENTRY-362.patch
>
>
> whatever Sentry Solr plugin integration with db store or file store, the
> create instance of DBProviderBackend of FIleProviderBackend should get the
> configuration from sentry-site.xml not hadoop configuration. The following
> code isn't correct:
> {code:title=SolrAuthzBinding.java}
> Configuration conf = getConf();
> providerBackend =(ProviderBackend)
> providerBackendConstructor.newInstance(new Object[] {conf, resourceName});
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
