You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Cheolsoo Park (JIRA)" <ji...@apache.org> on 2014/03/07 22:57:44 UTC

[jira] [Reopened] (PIG-3765) Ability to disable Pig commands and operators

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

Cheolsoo Park reopened PIG-3765:
--------------------------------


[~prkommireddi], I am reopening this jira. Your new tests fail with the following error-
{code}
Testcase: testWhitelist2 took 0.046 sec 
        Caused an ERROR
org.hamcrest.Matcher.describeMismatch(Ljava/lang/Object;Lorg/hamcrest/Description;)V
java.lang.NoSuchMethodError: org.hamcrest.Matcher.describeMismatch(Ljava/lang/Object;Lorg/hamcrest/Description;)V
        at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:18)
{code}

I think we're hitting this problem-
https://tedvinke.wordpress.com/2013/12/17/mixing-junit-hamcrest-and-mockito-explaining-nosuchmethoderror/

Can you take a look please?

> Ability to disable Pig commands and operators
> ---------------------------------------------
>
>                 Key: PIG-3765
>                 URL: https://issues.apache.org/jira/browse/PIG-3765
>             Project: Pig
>          Issue Type: New Feature
>          Components: documentation, grunt
>            Reporter: Prashant Kommireddi
>            Assignee: Prashant Kommireddi
>             Fix For: 0.13.0
>
>         Attachments: PIG-3765.patch, PIG-3765_2.patch, PIG-3765_3.patch, PIG-3765_4.patch, PIG-3765_5.patch
>
>
> This is an admin feature providing ability to blacklist or/and whitelist certain commands and operations. Pig exposes a few of these that could be not very safe in a multitenant environment. For example, "sh" invokes shell commands, "set" allows users to change non-final configs. While these are tremendously useful in general, having an ability to disable would make Pig a safer platform. The goal is to allow administrators to be able to have more control over user scripts. Default behaviour would still be the same - no filters applied on commands and operators.



--
This message was sent by Atlassian JIRA
(v6.2#6252)