Return-Path: X-Original-To: apmail-sentry-commits-archive@minotaur.apache.org Delivered-To: apmail-sentry-commits-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D1BAB10382 for ; Fri, 13 Feb 2015 07:00:39 +0000 (UTC) Received: (qmail 74034 invoked by uid 500); 13 Feb 2015 07:00:39 -0000 Delivered-To: apmail-sentry-commits-archive@sentry.apache.org Received: (qmail 73981 invoked by uid 500); 13 Feb 2015 07:00:39 -0000 Mailing-List: contact commits-help@sentry.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@sentry.incubator.apache.org Delivered-To: mailing list commits@sentry.incubator.apache.org Received: (qmail 73972 invoked by uid 99); 13 Feb 2015 07:00:39 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Feb 2015 07:00:39 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.3] (HELO mail.apache.org) (140.211.11.3) by apache.org (qpsmtpd/0.29) with SMTP; Fri, 13 Feb 2015 07:00:38 +0000 Received: (qmail 72941 invoked by uid 99); 13 Feb 2015 07:00:18 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Feb 2015 07:00:18 +0000 Date: Fri, 13 Feb 2015 07:00:18 +0000 (UTC) From: "Hadoop QA (JIRA)" To: commits@sentry.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (SENTRY-478) Solr Sentry plug-in integration with DB store MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ 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)