sentry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SENTRY-1037) Handle solr shell configuration in the same manner as sentry-binding
Date Fri, 29 Jan 2016 22:29:40 GMT

    [ https://issues.apache.org/jira/browse/SENTRY-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15124351#comment-15124351
] 

Hadoop QA commented on SENTRY-1037:
-----------------------------------

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12785254/SENTRY-1037.patch against master.

{color:green}Overall:{color} +1 all checks pass

{color:green}SUCCESS:{color} all tests passed

Console output: https://builds.apache.org/job/PreCommit-SENTRY-Build/1132/console

This message is automatically generated.

> Handle solr shell configuration in the same manner as sentry-binding
> --------------------------------------------------------------------
>
>                 Key: SENTRY-1037
>                 URL: https://issues.apache.org/jira/browse/SENTRY-1037
>             Project: Sentry
>          Issue Type: Bug
>          Components: Service, Solr Plugin
>    Affects Versions: 1.7.0
>            Reporter: Gregory Chanan
>            Assignee: Gregory Chanan
>             Fix For: 1.7.0
>
>         Attachments: SENTRY-1037.patch, SENTRY-1037.patch
>
>
> Today, the SentryShellSolr follows the same pattern as SentryShellHive, which is just
getting a "new Configuration()".  In order to connect to a service requiring kerberos, the
Configuration must have "hadoop.security.authentication" set to "kerberos" since the generic
client uses hadoop-auth to do the authentication.  But this will often not be set in the context
of Solr, which may not even have a hadoop-related configuration around.
> So, we should handle the configuration in the same way as we do for the binding; namely,
if the client intends to use kerberos, we set "hadoop.security.authentication" to "kerberos"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message