You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Prashant Kommireddi (JIRA)" <ji...@apache.org> on 2014/02/15 02:33:19 UTC

[jira] [Updated] (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 ]

Prashant Kommireddi updated PIG-3765:
-------------------------------------

    Attachment: PIG-3765.patch

First patch that handles disabling pig commands and operators via a blacklist or/and a whitelist. [~daijy] this is based on our conversation from earlier. I haven't included tests yet, but wanted to get this out to have more eyes on it.

> 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
>         Attachments: PIG-3765.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.1.5#6160)