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-1038) More strict checking of SOLR actions in shell
Date Tue, 02 Feb 2016 07:16:39 GMT

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

Hadoop QA commented on SENTRY-1038:
-----------------------------------

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

{color:red}Overall:{color} -1 due to 2 errors

{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed: org.apache.sentry.tests.e2e.dbprovider.TestDbConnections

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

This message is automatically generated.

> More strict checking of SOLR actions in shell
> ---------------------------------------------
>
>                 Key: SENTRY-1038
>                 URL: https://issues.apache.org/jira/browse/SENTRY-1038
>             Project: Sentry
>          Issue Type: Task
>          Components: Service
>    Affects Versions: 1.7.0
>            Reporter: Gregory Chanan
>            Assignee: Gregory Chanan
>             Fix For: 1.7.0
>
>         Attachments: SENTRY-1038.patch
>
>
> Currently, the client lets you specify bogus actions or no action at all.  The service
doesn't report anything back to the client in these cases, although it does seem to do the
correct thing (at least for bogus actions, it doesn't return the privilege when you list it).
 In order to improve the user experience, we can check this on the client side and give useful
hints.



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

Mime
View raw message