sentry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gregory Chanan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SENTRY-62) Solr binding should create a solr-usable Configuration to pass to the BackendProvider
Date Fri, 08 Nov 2013 21:08:17 GMT

     [ https://issues.apache.org/jira/browse/SENTRY-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gregory Chanan updated SENTRY-62:
---------------------------------

    Attachment: SENTRY-62v2.patch

> Solr binding should create a solr-usable Configuration to pass to the BackendProvider
> -------------------------------------------------------------------------------------
>
>                 Key: SENTRY-62
>                 URL: https://issues.apache.org/jira/browse/SENTRY-62
>             Project: Sentry
>          Issue Type: Improvement
>    Affects Versions: 1.3.0
>            Reporter: Gregory Chanan
>            Assignee: Gregory Chanan
>             Fix For: 1.3.0
>
>         Attachments: SENTRY-62v2.patch
>
>
> Today, the SolrAuthzBinding uses the SimpleFileProviderBackend, which ends up creating
a configuration via:
> {code}
> new Configuration();
> {code}
> the issue with this is this might not be the Configuration we want -- for example, in
a secure setup, it may not have all the authentication/authorization properties necessary
to connect to hdfs to read the sentry .ini file.  I'm not sure exactly how this works in hive,
but it may be because hive has the relevant core-site.xml, hdfs-site.xml in its classpath,
whereas in solr, this is uncommon.
> Solr does have a way to specify hdfs configs already via the HdfsDirectoryFactory and
HdfsUtils.  We should just reuse this.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message