[
https://issues.apache.org/jira/browse/SENTRY-478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14319671#comment-14319671
]
Hadoop QA commented on SENTRY-478:
----------------------------------
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12698644/SENTRY-478.011.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/437/console
This message is automatically generated.
> Solr Sentry plug-in integration with DB store
> ---------------------------------------------
>
> Key: SENTRY-478
> URL: https://issues.apache.org/jira/browse/SENTRY-478
> Project: Sentry
> Issue Type: New Feature
> Reporter: guoquan
> Assignee: guoquan
> Attachments: SENTRY-478.003.patch, SENTRY-478.004.patch,
> SENTRY-478.005.patch, SENTRY-478.006.patch, SENTRY-478.007.patch,
> SENTRY-478.008.patch, SENTRY-478.009.patch, SENTRY-478.010.patch,
> SENTRY-478.011.patch
>
>
> Currently Solr does support index-level security via sentry with file as
> backend privilege store. Using file as the backend store is simple, but there
> has some disadvantages as followings:
> 1. Can't satisfied with the needs of dynamically add, delete and update
> permissions
> 2. Can't be centrally managed and difficult to maintain
> According to the above disadvantages, The Solr Sentry plug-in integration
> with DB store is demanded. The Hive Sentry plug-in has already integration
> with DB store, but the Hive authorization model is different from the Solr
> authorization model.So this new feature depends on the generic authorization
> model(SENTRY-398).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
