You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pig.apache.org by ch...@apache.org on 2014/06/08 02:47:04 UTC
svn commit: r1601188 - in /pig/trunk: CHANGES.txt
src/docs/src/documentation/content/xdocs/admin.xml
Author: cheolsoo
Date: Sun Jun 8 00:47:04 2014
New Revision: 1601188
URL: http://svn.apache.org/r1601188
Log:
PIG-3990: ant docs is broken in trunk/branch-0.13 (cheolsoo)
Modified:
pig/trunk/CHANGES.txt
pig/trunk/src/docs/src/documentation/content/xdocs/admin.xml
Modified: pig/trunk/CHANGES.txt
URL: http://svn.apache.org/viewvc/pig/trunk/CHANGES.txt?rev=1601188&r1=1601187&r2=1601188&view=diff
==============================================================================
--- pig/trunk/CHANGES.txt (original)
+++ pig/trunk/CHANGES.txt Sun Jun 8 00:47:04 2014
@@ -173,6 +173,8 @@ PIG-3882: Multiquery off mode execution
BUG FIXES
+PIG-3990: ant docs is broken in trunk/branch-0.13 (cheolsoo)
+
PIG-3989: PIG_OPTS does not work with some version of HADOOP (daijy)
PIG-3739: The Warning_4 e2e test is broken in trunk (aniket486)
Modified: pig/trunk/src/docs/src/documentation/content/xdocs/admin.xml
URL: http://svn.apache.org/viewvc/pig/trunk/src/docs/src/documentation/content/xdocs/admin.xml?rev=1601188&r1=1601187&r2=1601188&view=diff
==============================================================================
--- pig/trunk/src/docs/src/documentation/content/xdocs/admin.xml (original)
+++ pig/trunk/src/docs/src/documentation/content/xdocs/admin.xml Sun Jun 8 00:47:04 2014
@@ -34,21 +34,26 @@
<!-- DISABLE PIG COMMANDS AND OPERATORS -->
<section>
- <title>Disabling Pig commands and operators</title>
- <p>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.</p>
- <p>There are two properties you can use to control what users are able to do</p>
+ <title>Disabling Pig commands and operators</title>
+ <p>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.</p>
+ <p>There are two properties you can use to control what users are able to do</p>
<ul>
<li>pig.blacklist</li>
<li>pig.whitelist</li>
</ul>
- <h4>Blacklisting</h4>
- <p>Set "pig.blacklist" to a comma-delimited set of operators and commands. For eg, <i>pig.blacklist=rm,kill,cross</i> would disable users from executing any of "rm", "kill" commands and "cross" operator.</p>
-
- <h4>Whitelisting</h4>
- <p>This is an even safer approach to disallowing functionality in Pig. Using this you will be able to disable all commands and operators that are not a part of the whitelist. For eg, <i>pig.whitelist=load,filter,store</i> will disallow every command and operator other than "load", "filter" and "store". </p>
- <h4>Note</h4>
+ <section>
+ <title>Blacklisting</title>
+ <p>Set "pig.blacklist" to a comma-delimited set of operators and commands. For eg, <strong>pig.blacklist=rm,kill,cross</strong> would disable users from executing any of "rm", "kill" commands and "cross" operator.</p>
+ </section>
+ <section>
+ <title>Whitelisting</title>
+ <p>This is an even safer approach to disallowing functionality in Pig. Using this you will be able to disable all commands and operators that are not a part of the whitelist. For eg, <strong>pig.whitelist=load,filter,store</strong> will disallow every command and operator other than "load", "filter" and "store".</p>
+ </section>
+ <section>
+ <title>Note</title>
<p>There should not be any conflicts between blacklist and whitelist. Make sure to have them entirely distinct or Pig will complain.</p>
+ </section>
</section>
-</body>
+ </body>
</document>