Modified: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.EncryptContent/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.EncryptContent/index.html?rev=1771896&r1=1771895&r2=1771896&view=diff
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.EncryptContent/index.html
 (original)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.EncryptContent/index.html
 Tue Nov 29 12:33:21 2016
@@ -1 +1 @@
-<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>EncryptContent</title><link rel="stylesheet" 
href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Encrypts or 
Decrypts a FlowFile using either symmetric encryption with a password and 
randomly generated salt, or asymmetric encryption using a public and secret 
key.</p><p><a href="additionalDetails.html">Additional 
Details...</a></p><h3>Tags: </h3><p>encryption, decryption, password, JCE, 
OpenPGP, PGP, GPG</p><h3>Properties: </h3><p>In the list below, the names of 
required properties appear in <strong>bold</strong>. Any other properties (not 
in bold) are considered optional. The table also indicates any default values, 
and whether a property is considered "sensitive", meaning that its value will 
be encrypted. Before entering a value in a sensitive property, ensure that the 
<strong>nifi.properties</strong> file has an entry for the property 
<strong>nifi.sensitive.props.
 key</strong>.</p><table id="properties"><tr><th>Name</th><th>Default 
Value</th><th>Allowable Values</th><th>Description</th></tr><tr><td 
id="name"><strong>Mode</strong></td><td id="default-value">Encrypt</td><td 
id="allowable-values"><ul><li>Encrypt</li><li>Decrypt</li></ul></td><td 
id="description">Specifies whether the content should be encrypted or 
decrypted</td></tr><tr><td id="name"><strong>Key Derivation 
Function</strong></td><td id="default-value">BCRYPT</td><td 
id="allowable-values"><ul><li>NiFi Legacy KDF <img 
src="../../html/images/iconInfo.png" alt="MD5 @ 1000 iterations" title="MD5 @ 
1000 iterations"></img></li><li>OpenSSL EVP_BytesToKey <img 
src="../../html/images/iconInfo.png" alt="Single iteration MD5 compatible with 
PKCS#5 v1.5" title="Single iteration MD5 compatible with PKCS#5 
v1.5"></img></li><li>Bcrypt <img src="../../html/images/iconInfo.png" 
alt="Bcrypt with configurable work factor. See Admin Guide" title="Bcrypt with 
configurable work factor. See Admin Guide"
 ></img></li><li>Scrypt <img src="../../html/images/iconInfo.png" alt="Scrypt 
 >with configurable cost parameters. See Admin Guide" title="Scrypt with 
 >configurable cost parameters. See Admin Guide"></img></li><li>PBKDF2 <img 
 >src="../../html/images/iconInfo.png" alt="PBKDF2 with configurable hash 
 >function and iteration count. See Admin Guide" title="PBKDF2 with 
 >configurable hash function and iteration count. See Admin 
 >Guide"></img></li><li>None <img src="../../html/images/iconInfo.png" alt="The 
 >cipher is given a raw key conforming to the algorithm specifications" 
 >title="The cipher is given a raw key conforming to the algorithm 
 >specifications"></img></li></ul></td><td id="description">Specifies the key 
 >derivation function to generate the key from the password (and 
 >salt)</td></tr><tr><td id="name"><strong>Encryption 
 >Algorithm</strong></td><td id="default-value">MD5_128AES</td><td 
 >id="allowable-values"><ul><li>MD5_128AES <img 
 >src="../../html/images/iconInfo.png" alt="org.apache.nifi.securi
 ty.util.EncryptionMethod@a518813[Algorithm 
name=PBEWITHMD5AND128BITAES-CBC-OPENSSL,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" 
title="org.apache.nifi.security.util.EncryptionMethod@a518813[Algorithm 
name=PBEWITHMD5AND128BITAES-CBC-OPENSSL,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>MD5_192AES <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHMD5AND192BITAES-CBC-OPENSSL,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHMD5AND192BITAES-CBC-OPENSSL,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>MD5_256AES <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm na
 me=PBEWITHMD5AND256BITAES-CBC-OPENSSL,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHMD5AND256BITAES-CBC-OPENSSL,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>MD5_DES <img src="../../html/images/iconInfo.png" 
alt="EncryptionMethod[Algorithm name=PBEWITHMD5ANDDES,Requires unlimited 
strength JCE policy=false,Algorithm Provider=BC,Compatible with strong 
KDFs=false,Keyed cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHMD5ANDDES,Requires unlimited strength JCE policy=false,Algorithm 
Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>MD5_RC2 <img src="../../html/images/iconInfo.png" 
alt="EncryptionMethod[Algorithm name=PBEWITHMD5ANDRC2,Requires unlimited 
strength JCE policy=false,Algorithm Provider=BC,Compatible with strong 
KDFs=false,Keye
 d cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHMD5ANDRC2,Requires unlimited strength JCE policy=false,Algorithm 
Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA1_RC2 <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHA1ANDRC2,Requires unlimited strength JCE policy=false,Algorithm 
Provider=BC,Compatible with strong KDFs=false,Keyed cipher=false]" 
title="EncryptionMethod[Algorithm name=PBEWITHSHA1ANDRC2,Requires unlimited 
strength JCE policy=false,Algorithm Provider=BC,Compatible with strong 
KDFs=false,Keyed cipher=false]"></img></li><li>SHA1_DES <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHA1ANDDES,Requires unlimited strength JCE policy=false,Algorithm 
Provider=BC,Compatible with strong KDFs=false,Keyed cipher=false]" 
title="EncryptionMethod[Algorithm name=PBEWITHSHA1ANDDES,Requires unlimited 
strength JCE policy=false,Algorithm Provider=BC,Compatible wi
 th strong KDFs=false,Keyed cipher=false]"></img></li><li>SHA_128AES <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND128BITAES-CBC-BC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND128BITAES-CBC-BC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA_192AES <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND192BITAES-CBC-BC,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND192BITAES-CBC-BC,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA_256AES <img src="../../html/images/iconInf
 o.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND256BITAES-CBC-BC,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND256BITAES-CBC-BC,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA_40RC2 <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND40BITRC2-CBC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND40BITRC2-CBC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA_128RC2 <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND128BITRC2-CBC,Requires unlimited strength JCE policy=fa
 lse,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND128BITRC2-CBC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA_40RC4 <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND40BITRC4,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND40BITRC4,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA_128RC4 <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND128BITRC4,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm name=PBEWITHS
 HAAND128BITRC4,Requires unlimited strength JCE policy=false,Algorithm 
Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA256_128AES <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHA256AND128BITAES-CBC-BC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHA256AND128BITAES-CBC-BC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA256_192AES <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHA256AND192BITAES-CBC-BC,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHA256AND192BITAES-CBC-BC,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,Com
 patible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA256_256AES <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHA256AND256BITAES-CBC-BC,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHA256AND256BITAES-CBC-BC,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA_2KEYTRIPLEDES <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND2-KEYTRIPLEDES-CBC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND2-KEYTRIPLEDES-CBC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA_3KEYTRIPLEDE
 S <img src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND3-KEYTRIPLEDES-CBC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND3-KEYTRIPLEDES-CBC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA_TWOFISH <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHAANDTWOFISH-CBC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHAANDTWOFISH-CBC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>PGP <img src="../../html/images/iconInfo.png" 
alt="EncryptionMethod[Algorithm name=PGP,Requires unlimited strength 
 JCE policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm name=PGP,Requires unlimited 
strength JCE policy=false,Algorithm Provider=BC,Compatible with strong 
KDFs=false,Keyed cipher=false]"></img></li><li>PGP_ASCII_ARMOR <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PGP-ASCII-ARMOR,Requires unlimited strength JCE policy=false,Algorithm 
Provider=BC,Compatible with strong KDFs=false,Keyed cipher=false]" 
title="EncryptionMethod[Algorithm name=PGP-ASCII-ARMOR,Requires unlimited 
strength JCE policy=false,Algorithm Provider=BC,Compatible with strong 
KDFs=false,Keyed cipher=false]"></img></li><li>AES_CBC <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=AES/CBC/PKCS7Padding,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=true,Keyed 
cipher=true]" title="EncryptionMethod[Algorithm 
name=AES/CBC/PKCS7Padding,Requires u
 nlimited strength JCE policy=false,Algorithm Provider=BC,Compatible with 
strong KDFs=true,Keyed cipher=true]"></img></li><li>AES_CTR <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=AES/CTR/NoPadding,Requires unlimited strength JCE policy=false,Algorithm 
Provider=BC,Compatible with strong KDFs=true,Keyed cipher=true]" 
title="EncryptionMethod[Algorithm name=AES/CTR/NoPadding,Requires unlimited 
strength JCE policy=false,Algorithm Provider=BC,Compatible with strong 
KDFs=true,Keyed cipher=true]"></img></li><li>AES_GCM <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=AES/GCM/NoPadding,Requires unlimited strength JCE policy=false,Algorithm 
Provider=BC,Compatible with strong KDFs=true,Keyed cipher=true]" 
title="EncryptionMethod[Algorithm name=AES/GCM/NoPadding,Requires unlimited 
strength JCE policy=false,Algorithm Provider=BC,Compatible with strong 
KDFs=true,Keyed cipher=true]"></img></li></ul></td><td id="description">The 
Encrypt
 ion Algorithm to use</td></tr><tr><td id="name"><strong>Allow insecure 
cryptographic modes</strong></td><td id="default-value">not-allowed</td><td 
id="allowable-values"><ul><li>Allowed <img src="../../html/images/iconInfo.png" 
alt="Operation will not be blocked and no alerts will be presented when unsafe 
combinations of encryption algorithms and passwords are provided" 
title="Operation will not be blocked and no alerts will be presented when 
unsafe combinations of encryption algorithms and passwords are 
provided"></img></li><li>Not Allowed <img src="../../html/images/iconInfo.png" 
alt="When set, operation will be blocked and alerts will be presented to the 
user if unsafe combinations of encryption algorithms and passwords are provided 
on a JVM with limited strength crypto. To fix this, see the Admin Guide." 
title="When set, operation will be blocked and alerts will be presented to the 
user if unsafe combinations of encryption algorithms and passwords are provided 
on a JVM with limit
 ed strength crypto. To fix this, see the Admin 
Guide."></img></li></ul></td><td id="description">Overrides the default 
behavior to prevent unsafe combinations of encryption algorithms and short 
passwords on JVMs with limited strength cryptographic jurisdiction 
policies</td></tr><tr><td id="name">Password</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
Password to use for encrypting or decrypting the data<br/><strong>Sensitive 
Property: true</strong></td></tr><tr><td id="name">Raw Key 
(hexadecimal)</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">In keyed encryption, this is 
the raw key, encoded in hexadecimal<br/><strong>Sensitive Property: 
true</strong></td></tr><tr><td id="name">Public Keyring File</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">In 
a PGP encrypt mode, this keyring contains the public key of the 
recipient</td></tr><tr><td id="name">Public Key User Id</td><
 td id="default-value"></td><td id="allowable-values"></td><td 
id="description">In a PGP encrypt mode, this user id of the 
recipient</td></tr><tr><td id="name">Private Keyring File</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">In 
a PGP decrypt mode, this keyring contains the private key of the 
recipient</td></tr><tr><td id="name">Private Keyring Passphrase</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">In 
a PGP decrypt mode, this is the private keyring 
passphrase<br/><strong>Sensitive Property: 
true</strong></td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>Any
 FlowFile that is successfully encrypted or decrypted will be routed to 
success</td></tr><tr><td>failure</td><td>Any FlowFile that cannot be encrypted 
or decrypted will be routed to failure</td></tr></table><h3>Reads Attributes: 
</h3>None specified.<h3>Writes Attributes: <
 /h3>None specified.</body></html>
\ No newline at end of file
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>EncryptContent</title><link rel="stylesheet" 
href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Encrypts or 
Decrypts a FlowFile using either symmetric encryption with a password and 
randomly generated salt, or asymmetric encryption using a public and secret 
key.</p><p><a href="additionalDetails.html">Additional 
Details...</a></p><h3>Tags: </h3><p>encryption, decryption, password, JCE, 
OpenPGP, PGP, GPG</p><h3>Properties: </h3><p>In the list below, the names of 
required properties appear in <strong>bold</strong>. Any other properties (not 
in bold) are considered optional. The table also indicates any default values, 
and whether a property is considered "sensitive", meaning that its value will 
be encrypted. Before entering a value in a sensitive property, ensure that the 
<strong>nifi.properties</strong> file has an entry for the property 
<strong>nifi.sensitive.props.
 key</strong>.</p><table id="properties"><tr><th>Name</th><th>Default 
Value</th><th>Allowable Values</th><th>Description</th></tr><tr><td 
id="name"><strong>Mode</strong></td><td id="default-value">Encrypt</td><td 
id="allowable-values"><ul><li>Encrypt</li><li>Decrypt</li></ul></td><td 
id="description">Specifies whether the content should be encrypted or 
decrypted</td></tr><tr><td id="name"><strong>Key Derivation 
Function</strong></td><td id="default-value">BCRYPT</td><td 
id="allowable-values"><ul><li>NiFi Legacy KDF <img 
src="../../html/images/iconInfo.png" alt="MD5 @ 1000 iterations" title="MD5 @ 
1000 iterations"></img></li><li>OpenSSL EVP_BytesToKey <img 
src="../../html/images/iconInfo.png" alt="Single iteration MD5 compatible with 
PKCS#5 v1.5" title="Single iteration MD5 compatible with PKCS#5 
v1.5"></img></li><li>Bcrypt <img src="../../html/images/iconInfo.png" 
alt="Bcrypt with configurable work factor. See Admin Guide" title="Bcrypt with 
configurable work factor. See Admin Guide"
 ></img></li><li>Scrypt <img src="../../html/images/iconInfo.png" alt="Scrypt 
 >with configurable cost parameters. See Admin Guide" title="Scrypt with 
 >configurable cost parameters. See Admin Guide"></img></li><li>PBKDF2 <img 
 >src="../../html/images/iconInfo.png" alt="PBKDF2 with configurable hash 
 >function and iteration count. See Admin Guide" title="PBKDF2 with 
 >configurable hash function and iteration count. See Admin 
 >Guide"></img></li><li>None <img src="../../html/images/iconInfo.png" alt="The 
 >cipher is given a raw key conforming to the algorithm specifications" 
 >title="The cipher is given a raw key conforming to the algorithm 
 >specifications"></img></li></ul></td><td id="description">Specifies the key 
 >derivation function to generate the key from the password (and 
 >salt)</td></tr><tr><td id="name"><strong>Encryption 
 >Algorithm</strong></td><td id="default-value">MD5_128AES</td><td 
 >id="allowable-values"><ul><li>MD5_128AES <img 
 >src="../../html/images/iconInfo.png" alt="org.apache.nifi.securi
 ty.util.EncryptionMethod@3db432c2[Algorithm 
name=PBEWITHMD5AND128BITAES-CBC-OPENSSL,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" 
title="org.apache.nifi.security.util.EncryptionMethod@3db432c2[Algorithm 
name=PBEWITHMD5AND128BITAES-CBC-OPENSSL,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>MD5_192AES <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHMD5AND192BITAES-CBC-OPENSSL,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHMD5AND192BITAES-CBC-OPENSSL,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>MD5_256AES <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
 name=PBEWITHMD5AND256BITAES-CBC-OPENSSL,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHMD5AND256BITAES-CBC-OPENSSL,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>MD5_DES <img src="../../html/images/iconInfo.png" 
alt="EncryptionMethod[Algorithm name=PBEWITHMD5ANDDES,Requires unlimited 
strength JCE policy=false,Algorithm Provider=BC,Compatible with strong 
KDFs=false,Keyed cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHMD5ANDDES,Requires unlimited strength JCE policy=false,Algorithm 
Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>MD5_RC2 <img src="../../html/images/iconInfo.png" 
alt="EncryptionMethod[Algorithm name=PBEWITHMD5ANDRC2,Requires unlimited 
strength JCE policy=false,Algorithm Provider=BC,Compatible with strong 
KDFs=false,Ke
 yed cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHMD5ANDRC2,Requires unlimited strength JCE policy=false,Algorithm 
Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA1_RC2 <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHA1ANDRC2,Requires unlimited strength JCE policy=false,Algorithm 
Provider=BC,Compatible with strong KDFs=false,Keyed cipher=false]" 
title="EncryptionMethod[Algorithm name=PBEWITHSHA1ANDRC2,Requires unlimited 
strength JCE policy=false,Algorithm Provider=BC,Compatible with strong 
KDFs=false,Keyed cipher=false]"></img></li><li>SHA1_DES <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHA1ANDDES,Requires unlimited strength JCE policy=false,Algorithm 
Provider=BC,Compatible with strong KDFs=false,Keyed cipher=false]" 
title="EncryptionMethod[Algorithm name=PBEWITHSHA1ANDDES,Requires unlimited 
strength JCE policy=false,Algorithm Provider=BC,Compatible 
 with strong KDFs=false,Keyed cipher=false]"></img></li><li>SHA_128AES <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND128BITAES-CBC-BC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND128BITAES-CBC-BC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA_192AES <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND192BITAES-CBC-BC,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND192BITAES-CBC-BC,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA_256AES <img src="../../html/images/iconI
 nfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND256BITAES-CBC-BC,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND256BITAES-CBC-BC,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA_40RC2 <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND40BITRC2-CBC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND40BITRC2-CBC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA_128RC2 <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND128BITRC2-CBC,Requires unlimited strength JCE policy=
 false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND128BITRC2-CBC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA_40RC4 <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND40BITRC4,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND40BITRC4,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA_128RC4 <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND128BITRC4,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm name=PBEWIT
 HSHAAND128BITRC4,Requires unlimited strength JCE policy=false,Algorithm 
Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA256_128AES <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHA256AND128BITAES-CBC-BC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHA256AND128BITAES-CBC-BC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA256_192AES <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHA256AND192BITAES-CBC-BC,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHA256AND192BITAES-CBC-BC,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,C
 ompatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA256_256AES <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHA256AND256BITAES-CBC-BC,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHA256AND256BITAES-CBC-BC,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA_2KEYTRIPLEDES <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND2-KEYTRIPLEDES-CBC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND2-KEYTRIPLEDES-CBC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA_3KEYTRIPLE
 DES <img src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND3-KEYTRIPLEDES-CBC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND3-KEYTRIPLEDES-CBC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA_TWOFISH <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHAANDTWOFISH-CBC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHAANDTWOFISH-CBC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>PGP <img src="../../html/images/iconInfo.png" 
alt="EncryptionMethod[Algorithm name=PGP,Requires unlimited strengt
 h JCE policy=false,Algorithm Provider=BC,Compatible with strong 
KDFs=false,Keyed cipher=false]" title="EncryptionMethod[Algorithm 
name=PGP,Requires unlimited strength JCE policy=false,Algorithm 
Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>PGP_ASCII_ARMOR <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PGP-ASCII-ARMOR,Requires unlimited strength JCE policy=false,Algorithm 
Provider=BC,Compatible with strong KDFs=false,Keyed cipher=false]" 
title="EncryptionMethod[Algorithm name=PGP-ASCII-ARMOR,Requires unlimited 
strength JCE policy=false,Algorithm Provider=BC,Compatible with strong 
KDFs=false,Keyed cipher=false]"></img></li><li>AES_CBC <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=AES/CBC/PKCS7Padding,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=true,Keyed 
cipher=true]" title="EncryptionMethod[Algorithm 
name=AES/CBC/PKCS7Padding,Requires
  unlimited strength JCE policy=false,Algorithm Provider=BC,Compatible with 
strong KDFs=true,Keyed cipher=true]"></img></li><li>AES_CTR <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=AES/CTR/NoPadding,Requires unlimited strength JCE policy=false,Algorithm 
Provider=BC,Compatible with strong KDFs=true,Keyed cipher=true]" 
title="EncryptionMethod[Algorithm name=AES/CTR/NoPadding,Requires unlimited 
strength JCE policy=false,Algorithm Provider=BC,Compatible with strong 
KDFs=true,Keyed cipher=true]"></img></li><li>AES_GCM <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=AES/GCM/NoPadding,Requires unlimited strength JCE policy=false,Algorithm 
Provider=BC,Compatible with strong KDFs=true,Keyed cipher=true]" 
title="EncryptionMethod[Algorithm name=AES/GCM/NoPadding,Requires unlimited 
strength JCE policy=false,Algorithm Provider=BC,Compatible with strong 
KDFs=true,Keyed cipher=true]"></img></li></ul></td><td id="description">The 
Encry
 ption Algorithm to use</td></tr><tr><td id="name"><strong>Allow insecure 
cryptographic modes</strong></td><td id="default-value">not-allowed</td><td 
id="allowable-values"><ul><li>Allowed <img src="../../html/images/iconInfo.png" 
alt="Operation will not be blocked and no alerts will be presented when unsafe 
combinations of encryption algorithms and passwords are provided" 
title="Operation will not be blocked and no alerts will be presented when 
unsafe combinations of encryption algorithms and passwords are 
provided"></img></li><li>Not Allowed <img src="../../html/images/iconInfo.png" 
alt="When set, operation will be blocked and alerts will be presented to the 
user if unsafe combinations of encryption algorithms and passwords are provided 
on a JVM with limited strength crypto. To fix this, see the Admin Guide." 
title="When set, operation will be blocked and alerts will be presented to the 
user if unsafe combinations of encryption algorithms and passwords are provided 
on a JVM with lim
 ited strength crypto. To fix this, see the Admin 
Guide."></img></li></ul></td><td id="description">Overrides the default 
behavior to prevent unsafe combinations of encryption algorithms and short 
passwords on JVMs with limited strength cryptographic jurisdiction 
policies</td></tr><tr><td id="name">Password</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
Password to use for encrypting or decrypting the data<br/><strong>Sensitive 
Property: true</strong></td></tr><tr><td id="name">Raw Key 
(hexadecimal)</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">In keyed encryption, this is 
the raw key, encoded in hexadecimal<br/><strong>Sensitive Property: 
true</strong></td></tr><tr><td id="name">Public Keyring File</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">In 
a PGP encrypt mode, this keyring contains the public key of the 
recipient</td></tr><tr><td id="name">Public Key User Id</td
 ><td id="default-value"></td><td id="allowable-values"></td><td 
 >id="description">In a PGP encrypt mode, this user id of the 
 >recipient</td></tr><tr><td id="name">Private Keyring File</td><td 
 >id="default-value"></td><td id="allowable-values"></td><td 
 >id="description">In a PGP decrypt mode, this keyring contains the private key 
 >of the recipient</td></tr><tr><td id="name">Private Keyring 
 >Passphrase</td><td id="default-value"></td><td id="allowable-values"></td><td 
 >id="description">In a PGP decrypt mode, this is the private keyring 
 >passphrase<br/><strong>Sensitive Property: 
 >true</strong></td></tr></table><h3>Relationships: </h3><table 
 >id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>Any
 > FlowFile that is successfully encrypted or decrypted will be routed to 
 >success</td></tr><tr><td>failure</td><td>Any FlowFile that cannot be 
 >encrypted or decrypted will be routed to failure</td></tr></table><h3>Reads 
 >Attributes: </h3>None specified.<h3>Writes Attributes:
  </h3>None specified.<h3>State management: </h3>This processor has no state 
management.<h3>Restricted: </h3></body></html>
\ No newline at end of file

Modified: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.EvaluateJsonPath/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.EvaluateJsonPath/index.html?rev=1771896&r1=1771895&r2=1771896&view=diff
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.EvaluateJsonPath/index.html
 (original)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.EvaluateJsonPath/index.html
 Tue Nov 29 12:33:21 2016
@@ -1 +1 @@
-<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>EvaluateJsonPath</title><link rel="stylesheet" 
href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Evaluates one or 
more JsonPath expressions against the content of a FlowFile. The results of 
those expressions are assigned to FlowFile Attributes or are written to the 
content of the FlowFile itself, depending on configuration of the Processor. 
JsonPaths are entered by adding user-defined properties; the name of the 
property maps to the Attribute Name into which the result will be placed (if 
the Destination is flowfile-attribute; otherwise, the property name is 
ignored). The value of the property must be a valid JsonPath expression. A 
Return Type of 'auto-detect' will make a determination based off the configured 
destination. When 'Destination' is set to 'flowfile-attribute,' a return type 
of 'scalar' will be used. When 'Destination' is set to 'flowfile-content,' a re
 turn type of 'JSON' will be used.If the JsonPath evaluates to a JSON array or 
JSON object and the Return Type is set to 'scalar' the FlowFile will be 
unmodified and will be routed to failure. A Return Type of JSON can return 
scalar values if the provided JsonPath evaluates to the specified value and 
will be routed as a match.If Destination is 'flowfile-content' and the JsonPath 
does not evaluate to a defined path, the FlowFile will be routed to 'unmatched' 
without having its contents modified. If Destination is flowfile-attribute and 
the expression matches nothing, attributes will be created with empty strings 
as the value, and the FlowFile will always be routed to 'matched.'</p><p><a 
href="additionalDetails.html">Additional Details...</a></p><h3>Tags: 
</h3><p>JSON, evaluate, JsonPath</p><h3>Properties: </h3><p>In the list below, 
the names of required properties appear in <strong>bold</strong>. Any other 
properties (not in bold) are considered optional. The table also indicates any 
 default values.</p><table id="properties"><tr><th>Name</th><th>Default 
Value</th><th>Allowable Values</th><th>Description</th></tr><tr><td 
id="name"><strong>Destination</strong></td><td 
id="default-value">flowfile-content</td><td 
id="allowable-values"><ul><li>flowfile-content</li><li>flowfile-attribute</li></ul></td><td
 id="description">Indicates whether the results of the JsonPath evaluation are 
written to the FlowFile content or a FlowFile attribute; if using attribute, 
must specify the Attribute Name property. If set to flowfile-content, only one 
JsonPath may be specified, and the property name is ignored.</td></tr><tr><td 
id="name"><strong>Return Type</strong></td><td 
id="default-value">auto-detect</td><td 
id="allowable-values"><ul><li>auto-detect</li><li>json</li><li>scalar</li></ul></td><td
 id="description">Indicates the desired return type of the JSON Path 
expressions.  Selecting 'auto-detect' will set the return type to 'json' for a 
Destination of 'flowfile-content', and 'sc
 alar' for a Destination of 'flowfile-attribute'.</td></tr><tr><td 
id="name"><strong>Path Not Found Behavior</strong></td><td 
id="default-value">ignore</td><td 
id="allowable-values"><ul><li>warn</li><li>ignore</li></ul></td><td 
id="description">Indicates how to handle missing JSON path expressions when 
destination is set to 'flowfile-attribute'. Selecting 'warn' will generate a 
warning when a JSON path expression is not found.</td></tr><tr><td 
id="name"><strong>Null Value Representation</strong></td><td 
id="default-value">empty string</td><td id="allowable-values"><ul><li>empty 
string</li><li>the string 'null'</li></ul></td><td id="description">Indicates 
the desired representation of JSON Path expressions resulting in a null 
value.</td></tr></table><h3>Dynamic Properties: </h3><p>Dynamic Properties 
allow the user to specify both the name and value of a property.<table 
id="dynamic-properties"><tr><th>Name</th><th>Value</th><th>Description</th></tr><tr><td
 id="name">A FlowFile attribut
 e(if &lt;Destination&gt; is set to 'flowfile-attribute')</td><td id="value">A 
JsonPath expression</td><td>If &lt;Destination&gt;='flowfile-attribute' then 
that FlowFile attribute will be set to any JSON objects that match the 
JsonPath.  If &lt;Destination&gt;='flowfile-content' then the FlowFile content 
will be updated to any JSON objects that match the 
JsonPath.</td></tr></table></p><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>failure</td><td>FlowFiles
 are routed to this relationship when the JsonPath cannot be evaluated against 
the content of the FlowFile; for instance, if the FlowFile is not valid 
JSON</td></tr><tr><td>unmatched</td><td>FlowFiles are routed to this 
relationship when the JsonPath does not match the content of the FlowFile and 
the Destination is set to 
flowfile-content</td></tr><tr><td>matched</td><td>FlowFiles are routed to this 
relationship when the JsonPath is successfully evaluated and the FlowFile is 
modif
 ied as a result</td></tr></table><h3>Reads Attributes: </h3>None 
specified.<h3>Writes Attributes: </h3>None specified.</body></html>
\ No newline at end of file
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>EvaluateJsonPath</title><link rel="stylesheet" 
href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Evaluates one or 
more JsonPath expressions against the content of a FlowFile. The results of 
those expressions are assigned to FlowFile Attributes or are written to the 
content of the FlowFile itself, depending on configuration of the Processor. 
JsonPaths are entered by adding user-defined properties; the name of the 
property maps to the Attribute Name into which the result will be placed (if 
the Destination is flowfile-attribute; otherwise, the property name is 
ignored). The value of the property must be a valid JsonPath expression. A 
Return Type of 'auto-detect' will make a determination based off the configured 
destination. When 'Destination' is set to 'flowfile-attribute,' a return type 
of 'scalar' will be used. When 'Destination' is set to 'flowfile-content,' a re
 turn type of 'JSON' will be used.If the JsonPath evaluates to a JSON array or 
JSON object and the Return Type is set to 'scalar' the FlowFile will be 
unmodified and will be routed to failure. A Return Type of JSON can return 
scalar values if the provided JsonPath evaluates to the specified value and 
will be routed as a match.If Destination is 'flowfile-content' and the JsonPath 
does not evaluate to a defined path, the FlowFile will be routed to 'unmatched' 
without having its contents modified. If Destination is flowfile-attribute and 
the expression matches nothing, attributes will be created with empty strings 
as the value, and the FlowFile will always be routed to 'matched.'</p><p><a 
href="additionalDetails.html">Additional Details...</a></p><h3>Tags: 
</h3><p>JSON, evaluate, JsonPath</p><h3>Properties: </h3><p>In the list below, 
the names of required properties appear in <strong>bold</strong>. Any other 
properties (not in bold) are considered optional. The table also indicates any 
 default values.</p><table id="properties"><tr><th>Name</th><th>Default 
Value</th><th>Allowable Values</th><th>Description</th></tr><tr><td 
id="name"><strong>Destination</strong></td><td 
id="default-value">flowfile-content</td><td 
id="allowable-values"><ul><li>flowfile-content</li><li>flowfile-attribute</li></ul></td><td
 id="description">Indicates whether the results of the JsonPath evaluation are 
written to the FlowFile content or a FlowFile attribute; if using attribute, 
must specify the Attribute Name property. If set to flowfile-content, only one 
JsonPath may be specified, and the property name is ignored.</td></tr><tr><td 
id="name"><strong>Return Type</strong></td><td 
id="default-value">auto-detect</td><td 
id="allowable-values"><ul><li>auto-detect</li><li>json</li><li>scalar</li></ul></td><td
 id="description">Indicates the desired return type of the JSON Path 
expressions.  Selecting 'auto-detect' will set the return type to 'json' for a 
Destination of 'flowfile-content', and 'sc
 alar' for a Destination of 'flowfile-attribute'.</td></tr><tr><td 
id="name"><strong>Path Not Found Behavior</strong></td><td 
id="default-value">ignore</td><td 
id="allowable-values"><ul><li>warn</li><li>ignore</li></ul></td><td 
id="description">Indicates how to handle missing JSON path expressions when 
destination is set to 'flowfile-attribute'. Selecting 'warn' will generate a 
warning when a JSON path expression is not found.</td></tr><tr><td 
id="name"><strong>Null Value Representation</strong></td><td 
id="default-value">empty string</td><td id="allowable-values"><ul><li>empty 
string</li><li>the string 'null'</li></ul></td><td id="description">Indicates 
the desired representation of JSON Path expressions resulting in a null 
value.</td></tr></table><h3>Dynamic Properties: </h3><p>Dynamic Properties 
allow the user to specify both the name and value of a property.<table 
id="dynamic-properties"><tr><th>Name</th><th>Value</th><th>Description</th></tr><tr><td
 id="name">A FlowFile attribut
 e(if &lt;Destination&gt; is set to 'flowfile-attribute')</td><td id="value">A 
JsonPath expression</td><td>If &lt;Destination&gt;='flowfile-attribute' then 
that FlowFile attribute will be set to any JSON objects that match the 
JsonPath.  If &lt;Destination&gt;='flowfile-content' then the FlowFile content 
will be updated to any JSON objects that match the 
JsonPath.</td></tr></table></p><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>failure</td><td>FlowFiles
 are routed to this relationship when the JsonPath cannot be evaluated against 
the content of the FlowFile; for instance, if the FlowFile is not valid 
JSON</td></tr><tr><td>unmatched</td><td>FlowFiles are routed to this 
relationship when the JsonPath does not match the content of the FlowFile and 
the Destination is set to 
flowfile-content</td></tr><tr><td>matched</td><td>FlowFiles are routed to this 
relationship when the JsonPath is successfully evaluated and the FlowFile is 
modif
 ied as a result</td></tr></table><h3>Reads Attributes: </h3>None 
specified.<h3>Writes Attributes: </h3>None specified.<h3>State management: 
</h3>This processor has no state management.<h3>Restricted: </h3></body></html>
\ No newline at end of file

Modified: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.EvaluateXPath/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.EvaluateXPath/index.html?rev=1771896&r1=1771895&r2=1771896&view=diff
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.EvaluateXPath/index.html
 (original)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.EvaluateXPath/index.html
 Tue Nov 29 12:33:21 2016
@@ -1 +1 @@
-<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>EvaluateXPath</title><link rel="stylesheet" 
href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Evaluates one or 
more XPaths against the content of a FlowFile. The results of those XPaths are 
assigned to FlowFile Attributes or are written to the content of the FlowFile 
itself, depending on configuration of the Processor. XPaths are entered by 
adding user-defined properties; the name of the property maps to the Attribute 
Name into which the result will be placed (if the Destination is 
flowfile-attribute; otherwise, the property name is ignored). The value of the 
property must be a valid XPath expression. If the XPath evaluates to more than 
one node and the Return Type is set to 'nodeset' (either directly, or via 
'auto-detect' with a Destination of 'flowfile-content'), the FlowFile will be 
unmodified and will be routed to failure. If the XPath does not evaluate to a N
 ode, the FlowFile will be routed to 'unmatched' without having its contents 
modified. If Destination is flowfile-attribute and the expression matches 
nothing, attributes will be created with empty strings as the value, and the 
FlowFile will always be routed to 'matched'</p><h3>Tags: </h3><p>XML, evaluate, 
XPath</p><h3>Properties: </h3><p>In the list below, the names of required 
properties appear in <strong>bold</strong>. Any other properties (not in bold) 
are considered optional. The table also indicates any default values.</p><table 
id="properties"><tr><th>Name</th><th>Default Value</th><th>Allowable 
Values</th><th>Description</th></tr><tr><td 
id="name"><strong>Destination</strong></td><td 
id="default-value">flowfile-content</td><td 
id="allowable-values"><ul><li>flowfile-content</li><li>flowfile-attribute</li></ul></td><td
 id="description">Indicates whether the results of the XPath evaluation are 
written to the FlowFile content or a FlowFile attribute; if using attribute, 
must spec
 ify the Attribute Name property. If set to flowfile-content, only one XPath 
may be specified, and the property name is ignored.</td></tr><tr><td 
id="name"><strong>Return Type</strong></td><td 
id="default-value">auto-detect</td><td 
id="allowable-values"><ul><li>auto-detect</li><li>nodeset</li><li>string</li></ul></td><td
 id="description">Indicates the desired return type of the Xpath expressions.  
Selecting 'auto-detect' will set the return type to 'nodeset' for a Destination 
of 'flowfile-content', and 'string' for a Destination of 
'flowfile-attribute'.</td></tr></table><h3>Dynamic Properties: </h3><p>Dynamic 
Properties allow the user to specify both the name and value of a 
property.<table 
id="dynamic-properties"><tr><th>Name</th><th>Value</th><th>Description</th></tr><tr><td
 id="name">A FlowFile attribute(if &lt;Destination&gt; is set to 
'flowfile-attribute'</td><td id="value">An XPath expression</td><td>If 
&lt;Destination&gt;='flowfile-attribute' then the FlowFile attribute is set 
 to the result of the XPath Expression.  If 
&lt;Destination&gt;='flowfile-content' then the FlowFile content is set to the 
result of the XPath Expression.</td></tr></table></p><h3>Relationships: 
</h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>failure</td><td>FlowFiles
 are routed to this relationship when the XPath cannot be evaluated against the 
content of the FlowFile; for instance, if the FlowFile is not valid XML, or if 
the Return Type is 'nodeset' and the XPath evaluates to multiple 
nodes</td></tr><tr><td>unmatched</td><td>FlowFiles are routed to this 
relationship when the XPath does not match the content of the FlowFile and the 
Destination is set to 
flowfile-content</td></tr><tr><td>matched</td><td>FlowFiles are routed to this 
relationship when the XPath is successfully evaluated and the FlowFile is 
modified as a result</td></tr></table><h3>Reads Attributes: </h3>None 
specified.<h3>Writes Attributes: </h3><table id="writes-attributes"><tr><th>Nam
 e</th><th>Description</th></tr><tr><td>user-defined</td><td>This processor 
adds user-defined attributes if the &lt;Destination&gt; property is set to 
flowfile-attribute.</td></tr></table></body></html>
\ No newline at end of file
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>EvaluateXPath</title><link rel="stylesheet" 
href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Evaluates one or 
more XPaths against the content of a FlowFile. The results of those XPaths are 
assigned to FlowFile Attributes or are written to the content of the FlowFile 
itself, depending on configuration of the Processor. XPaths are entered by 
adding user-defined properties; the name of the property maps to the Attribute 
Name into which the result will be placed (if the Destination is 
flowfile-attribute; otherwise, the property name is ignored). The value of the 
property must be a valid XPath expression. If the XPath evaluates to more than 
one node and the Return Type is set to 'nodeset' (either directly, or via 
'auto-detect' with a Destination of 'flowfile-content'), the FlowFile will be 
unmodified and will be routed to failure. If the XPath does not evaluate to a N
 ode, the FlowFile will be routed to 'unmatched' without having its contents 
modified. If Destination is flowfile-attribute and the expression matches 
nothing, attributes will be created with empty strings as the value, and the 
FlowFile will always be routed to 'matched'</p><h3>Tags: </h3><p>XML, evaluate, 
XPath</p><h3>Properties: </h3><p>In the list below, the names of required 
properties appear in <strong>bold</strong>. Any other properties (not in bold) 
are considered optional. The table also indicates any default values.</p><table 
id="properties"><tr><th>Name</th><th>Default Value</th><th>Allowable 
Values</th><th>Description</th></tr><tr><td 
id="name"><strong>Destination</strong></td><td 
id="default-value">flowfile-content</td><td 
id="allowable-values"><ul><li>flowfile-content</li><li>flowfile-attribute</li></ul></td><td
 id="description">Indicates whether the results of the XPath evaluation are 
written to the FlowFile content or a FlowFile attribute; if using attribute, 
must spec
 ify the Attribute Name property. If set to flowfile-content, only one XPath 
may be specified, and the property name is ignored.</td></tr><tr><td 
id="name"><strong>Return Type</strong></td><td 
id="default-value">auto-detect</td><td 
id="allowable-values"><ul><li>auto-detect</li><li>nodeset</li><li>string</li></ul></td><td
 id="description">Indicates the desired return type of the Xpath expressions.  
Selecting 'auto-detect' will set the return type to 'nodeset' for a Destination 
of 'flowfile-content', and 'string' for a Destination of 
'flowfile-attribute'.</td></tr></table><h3>Dynamic Properties: </h3><p>Dynamic 
Properties allow the user to specify both the name and value of a 
property.<table 
id="dynamic-properties"><tr><th>Name</th><th>Value</th><th>Description</th></tr><tr><td
 id="name">A FlowFile attribute(if &lt;Destination&gt; is set to 
'flowfile-attribute'</td><td id="value">An XPath expression</td><td>If 
&lt;Destination&gt;='flowfile-attribute' then the FlowFile attribute is set 
 to the result of the XPath Expression.  If 
&lt;Destination&gt;='flowfile-content' then the FlowFile content is set to the 
result of the XPath Expression.</td></tr></table></p><h3>Relationships: 
</h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>failure</td><td>FlowFiles
 are routed to this relationship when the XPath cannot be evaluated against the 
content of the FlowFile; for instance, if the FlowFile is not valid XML, or if 
the Return Type is 'nodeset' and the XPath evaluates to multiple 
nodes</td></tr><tr><td>unmatched</td><td>FlowFiles are routed to this 
relationship when the XPath does not match the content of the FlowFile and the 
Destination is set to 
flowfile-content</td></tr><tr><td>matched</td><td>FlowFiles are routed to this 
relationship when the XPath is successfully evaluated and the FlowFile is 
modified as a result</td></tr></table><h3>Reads Attributes: </h3>None 
specified.<h3>Writes Attributes: </h3><table id="writes-attributes"><tr><th>Nam
 e</th><th>Description</th></tr><tr><td>user-defined</td><td>This processor 
adds user-defined attributes if the &lt;Destination&gt; property is set to 
flowfile-attribute.</td></tr></table><h3>State management: </h3>This processor 
has no state management.<h3>Restricted: </h3></body></html>
\ No newline at end of file

Modified: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.EvaluateXQuery/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.EvaluateXQuery/index.html?rev=1771896&r1=1771895&r2=1771896&view=diff
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.EvaluateXQuery/index.html
 (original)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.EvaluateXQuery/index.html
 Tue Nov 29 12:33:21 2016
@@ -1 +1 @@
-<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>EvaluateXQuery</title><link rel="stylesheet" 
href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Evaluates one or 
more XQueries against the content of a FlowFile.  The results of those XQueries 
are assigned to FlowFile Attributes or are written to the content of the 
FlowFile itself, depending on configuration of the Processor.  XQueries are 
entered by adding user-defined properties; the name of the property maps to the 
Attribute Name into which the result will be placed (if the Destination is 
'flowfile-attribute'; otherwise, the property name is ignored).  The value of 
the property must be a valid XQuery.  If the XQuery returns more than one 
result, new attributes or FlowFiles (for Destinations of 'flowfile-attribute' 
or 'flowfile-content' respectively) will be created for each result (attributes 
will have a '.n' one-up number appended to the specified attribute nam
 e).  If any provided XQuery returns a result, the FlowFile(s) will be routed 
to 'matched'. If no provided XQuery returns a result, the FlowFile will be 
routed to 'unmatched'.  If the Destination is 'flowfile-attribute' and the 
XQueries matche nothing, no attributes will be applied to the 
FlowFile.</p><p><a href="additionalDetails.html">Additional 
Details...</a></p><h3>Tags: </h3><p>XML, evaluate, XPath, 
XQuery</p><h3>Properties: </h3><p>In the list below, the names of required 
properties appear in <strong>bold</strong>. Any other properties (not in bold) 
are considered optional. The table also indicates any default values.</p><table 
id="properties"><tr><th>Name</th><th>Default Value</th><th>Allowable 
Values</th><th>Description</th></tr><tr><td 
id="name"><strong>Destination</strong></td><td 
id="default-value">flowfile-content</td><td 
id="allowable-values"><ul><li>flowfile-content</li><li>flowfile-attribute</li></ul></td><td
 id="description">Indicates whether the results of the XQuery
  evaluation are written to the FlowFile content or a FlowFile attribute. If 
set to &lt;flowfile-content&gt;, only one XQuery may be specified and the 
property name is ignored.  If set to &lt;flowfile-attribute&gt; and the XQuery 
returns more than one result, multiple attributes will be added to theFlowFile, 
each named with a '.n' one-up number appended to the specified attribute 
name</td></tr><tr><td id="name"><strong>Output: Method</strong></td><td 
id="default-value">xml</td><td 
id="allowable-values"><ul><li>xml</li><li>html</li><li>text</li></ul></td><td 
id="description">Identifies the overall method that should be used for 
outputting a result tree.</td></tr><tr><td id="name"><strong>Output: Omit XML 
Declaration</strong></td><td id="default-value">false</td><td 
id="allowable-values"></td><td id="description">Specifies whether the processor 
should output an XML declaration when transforming a result 
tree.</td></tr><tr><td id="name"><strong>Output: Indent</strong></td><td 
id="defaul
 t-value">false</td><td id="allowable-values"></td><td 
id="description">Specifies whether the processor may add additional whitespace 
when outputting a result tree.</td></tr></table><h3>Dynamic Properties: 
</h3><p>Dynamic Properties allow the user to specify both the name and value of 
a property.<table 
id="dynamic-properties"><tr><th>Name</th><th>Value</th><th>Description</th></tr><tr><td
 id="name">A FlowFile attribute(if &lt;Destination&gt; is set to 
'flowfile-attribute'</td><td id="value">An XQuery</td><td>If 
&lt;Destination&gt;='flowfile-attribute' then the FlowFile attribute is set to 
the result of the XQuery.  If &lt;Destination&gt;='flowfile-content' then the 
FlowFile content is set to the result of the 
XQuery.</td></tr></table></p><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>failure</td><td>FlowFiles
 are routed to this relationship when the XQuery cannot be evaluated against 
the content of the FlowFile.</td></tr><tr><td>un
 matched</td><td>FlowFiles are routed to this relationship when the XQuery does 
not match the content of the FlowFile and the Destination is set to 
flowfile-content</td></tr><tr><td>matched</td><td>FlowFiles are routed to this 
relationship when the XQuery is successfully evaluated and the FlowFile is 
modified as a result</td></tr></table><h3>Reads Attributes: </h3>None 
specified.<h3>Writes Attributes: </h3><table 
id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>user-defined</td><td>This
 processor adds user-defined attributes if the &lt;Destination&gt; property is 
set to flowfile-attribute .</td></tr></table></body></html>
\ No newline at end of file
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>EvaluateXQuery</title><link rel="stylesheet" 
href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Evaluates one or 
more XQueries against the content of a FlowFile.  The results of those XQueries 
are assigned to FlowFile Attributes or are written to the content of the 
FlowFile itself, depending on configuration of the Processor.  XQueries are 
entered by adding user-defined properties; the name of the property maps to the 
Attribute Name into which the result will be placed (if the Destination is 
'flowfile-attribute'; otherwise, the property name is ignored).  The value of 
the property must be a valid XQuery.  If the XQuery returns more than one 
result, new attributes or FlowFiles (for Destinations of 'flowfile-attribute' 
or 'flowfile-content' respectively) will be created for each result (attributes 
will have a '.n' one-up number appended to the specified attribute nam
 e).  If any provided XQuery returns a result, the FlowFile(s) will be routed 
to 'matched'. If no provided XQuery returns a result, the FlowFile will be 
routed to 'unmatched'.  If the Destination is 'flowfile-attribute' and the 
XQueries matche nothing, no attributes will be applied to the 
FlowFile.</p><p><a href="additionalDetails.html">Additional 
Details...</a></p><h3>Tags: </h3><p>XML, evaluate, XPath, 
XQuery</p><h3>Properties: </h3><p>In the list below, the names of required 
properties appear in <strong>bold</strong>. Any other properties (not in bold) 
are considered optional. The table also indicates any default values.</p><table 
id="properties"><tr><th>Name</th><th>Default Value</th><th>Allowable 
Values</th><th>Description</th></tr><tr><td 
id="name"><strong>Destination</strong></td><td 
id="default-value">flowfile-content</td><td 
id="allowable-values"><ul><li>flowfile-content</li><li>flowfile-attribute</li></ul></td><td
 id="description">Indicates whether the results of the XQuery
  evaluation are written to the FlowFile content or a FlowFile attribute. If 
set to &lt;flowfile-content&gt;, only one XQuery may be specified and the 
property name is ignored.  If set to &lt;flowfile-attribute&gt; and the XQuery 
returns more than one result, multiple attributes will be added to theFlowFile, 
each named with a '.n' one-up number appended to the specified attribute 
name</td></tr><tr><td id="name"><strong>Output: Method</strong></td><td 
id="default-value">xml</td><td 
id="allowable-values"><ul><li>xml</li><li>html</li><li>text</li></ul></td><td 
id="description">Identifies the overall method that should be used for 
outputting a result tree.</td></tr><tr><td id="name"><strong>Output: Omit XML 
Declaration</strong></td><td id="default-value">false</td><td 
id="allowable-values"></td><td id="description">Specifies whether the processor 
should output an XML declaration when transforming a result 
tree.</td></tr><tr><td id="name"><strong>Output: Indent</strong></td><td 
id="defaul
 t-value">false</td><td id="allowable-values"></td><td 
id="description">Specifies whether the processor may add additional whitespace 
when outputting a result tree.</td></tr></table><h3>Dynamic Properties: 
</h3><p>Dynamic Properties allow the user to specify both the name and value of 
a property.<table 
id="dynamic-properties"><tr><th>Name</th><th>Value</th><th>Description</th></tr><tr><td
 id="name">A FlowFile attribute(if &lt;Destination&gt; is set to 
'flowfile-attribute'</td><td id="value">An XQuery</td><td>If 
&lt;Destination&gt;='flowfile-attribute' then the FlowFile attribute is set to 
the result of the XQuery.  If &lt;Destination&gt;='flowfile-content' then the 
FlowFile content is set to the result of the 
XQuery.</td></tr></table></p><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>failure</td><td>FlowFiles
 are routed to this relationship when the XQuery cannot be evaluated against 
the content of the FlowFile.</td></tr><tr><td>un
 matched</td><td>FlowFiles are routed to this relationship when the XQuery does 
not match the content of the FlowFile and the Destination is set to 
flowfile-content</td></tr><tr><td>matched</td><td>FlowFiles are routed to this 
relationship when the XQuery is successfully evaluated and the FlowFile is 
modified as a result</td></tr></table><h3>Reads Attributes: </h3>None 
specified.<h3>Writes Attributes: </h3><table 
id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>user-defined</td><td>This
 processor adds user-defined attributes if the &lt;Destination&gt; property is 
set to flowfile-attribute .</td></tr></table><h3>State management: </h3>This 
processor has no state management.<h3>Restricted: </h3></body></html>
\ No newline at end of file

Modified: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ExecuteProcess/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ExecuteProcess/index.html?rev=1771896&r1=1771895&r2=1771896&view=diff
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ExecuteProcess/index.html
 (original)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ExecuteProcess/index.html
 Tue Nov 29 12:33:21 2016
@@ -1 +1 @@
-<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>ExecuteProcess</title><link rel="stylesheet" 
href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Runs an operating 
system command specified by the user and writes the output of that command to a 
FlowFile. If the command is expected to be long-running, the Processor can 
output the partial data on a specified interval. When this option is used, the 
output is expected to be in textual format, as it typically does not make sense 
to split binary data on arbitrary time-based intervals.</p><h3>Tags: 
</h3><p>command, process, source, external, invoke, script</p><h3>Properties: 
</h3><p>In the list below, the names of required properties appear in 
<strong>bold</strong>. Any other properties (not in bold) are considered 
optional. The table also indicates any default values.</p><table 
id="properties"><tr><th>Name</th><th>Default Value</th><th>Allowable 
Values</th><th>Descriptio
 n</th></tr><tr><td id="name"><strong>Command</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Specifies the command to be executed; if just the name of an 
executable is provided, it must be in the user's environment 
PATH.</td></tr><tr><td id="name">Command Arguments</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
arguments to supply to the executable delimited by white space. White space can 
be escaped by enclosing it in double-quotes.</td></tr><tr><td id="name">Batch 
Duration</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">If the process is expected to be long-running and produce 
textual output, a batch duration can be specified so that the output will be 
captured for this amount of time and a FlowFile will then be sent out with the 
results and a new FlowFile will be started, rather than waiting for the process 
to finish before sending out the results</td></tr><tr
 ><td id="name">Redirect Error Stream</td><td id="default-value">false</td><td 
 >id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
 >id="description">If true will redirect any error stream output of the process 
 >to the output stream. This is particularly helpful for processes which write 
 >extensively to the error stream or for troubleshooting.</td></tr><tr><td 
 >id="name"><strong>Argument Delimiter</strong></td><td id="default-value"> 
 ></td><td id="allowable-values"></td><td id="description">Delimiter to use to 
 >separate arguments for a command [default: space]. Must be a single 
 >character.</td></tr></table><h3>Dynamic Properties: </h3><p>Dynamic 
 >Properties allow the user to specify both the name and value of a 
 >property.<table 
 >id="dynamic-properties"><tr><th>Name</th><th>Value</th><th>Description</th></tr><tr><td
 > id="name">An environment variable name</td><td id="value">An environment 
 >variable value</td><td>These environment variables are passed to the process 
 >spawned by this P
 rocessor</td></tr></table></p><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>All
 created FlowFiles are routed to this relationship</td></tr></table><h3>Reads 
Attributes: </h3>None specified.<h3>Writes Attributes: </h3>None 
specified.</body></html>
\ No newline at end of file
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>ExecuteProcess</title><link rel="stylesheet" 
href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Runs an operating 
system command specified by the user and writes the output of that command to a 
FlowFile. If the command is expected to be long-running, the Processor can 
output the partial data on a specified interval. When this option is used, the 
output is expected to be in textual format, as it typically does not make sense 
to split binary data on arbitrary time-based intervals.</p><h3>Tags: 
</h3><p>command, process, source, external, invoke, script, 
restricted</p><h3>Properties: </h3><p>In the list below, the names of required 
properties appear in <strong>bold</strong>. Any other properties (not in bold) 
are considered optional. The table also indicates any default values, and 
whether a property supports the <a 
href="../../html/expression-language-guide.html">NiFi
  Expression Language</a>.</p><table 
id="properties"><tr><th>Name</th><th>Default Value</th><th>Allowable 
Values</th><th>Description</th></tr><tr><td 
id="name"><strong>Command</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Specifies the command to be 
executed; if just the name of an executable is provided, it must be in the 
user's environment PATH.</td></tr><tr><td id="name">Command Arguments</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
arguments to supply to the executable delimited by white space. White space can 
be escaped by enclosing it in double-quotes.<br/><strong>Supports Expression 
Language: true</strong></td></tr><tr><td id="name">Batch Duration</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">If 
the process is expected to be long-running and produce textual output, a batch 
duration can be specified so that the output will be captured for this amount o
 f time and a FlowFile will then be sent out with the results and a new 
FlowFile will be started, rather than waiting for the process to finish before 
sending out the results</td></tr><tr><td id="name">Redirect Error 
Stream</td><td id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">If true will redirect any error stream output of the process 
to the output stream. This is particularly helpful for processes which write 
extensively to the error stream or for troubleshooting.</td></tr><tr><td 
id="name"><strong>Argument Delimiter</strong></td><td id="default-value"> 
</td><td id="allowable-values"></td><td id="description">Delimiter to use to 
separate arguments for a command [default: space]. Must be a single 
character.</td></tr></table><h3>Dynamic Properties: </h3><p>Dynamic Properties 
allow the user to specify both the name and value of a property.<table 
id="dynamic-properties"><tr><th>Name</th><th>Value</th><th>Descriptio
 n</th></tr><tr><td id="name">An environment variable name</td><td 
id="value">An environment variable value</td><td>These environment variables 
are passed to the process spawned by this 
Processor</td></tr></table></p><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>All
 created FlowFiles are routed to this relationship</td></tr></table><h3>Reads 
Attributes: </h3>None specified.<h3>Writes Attributes: </h3>None 
specified.<h3>State management: </h3>This processor has no state 
management.<h3>Restricted: </h3><td>Provides operator the ability to execute 
arbitrary code assuming all permissions that NiFi has.</td></body></html>
\ No newline at end of file

Modified: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ExecuteSQL/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ExecuteSQL/index.html?rev=1771896&r1=1771895&r2=1771896&view=diff
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ExecuteSQL/index.html
 (original)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ExecuteSQL/index.html
 Tue Nov 29 12:33:21 2016
@@ -1 +1 @@
-<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>ExecuteSQL</title><link rel="stylesheet" 
href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Execute provided 
SQL select query. Query result will be converted to Avro format. Streaming is 
used so arbitrarily large result sets are supported. This processor can be 
scheduled to run on a timer, or cron expression, using the standard scheduling 
methods, or it can be triggered by an incoming FlowFile. If it is triggered by 
an incoming FlowFile, then attributes of that FlowFile will be available when 
evaluating the select query. FlowFile attribute 'executesql.row.count' 
indicates how many rows were selected.</p><h3>Tags: </h3><p>sql, select, jdbc, 
query, database</p><h3>Properties: </h3><p>In the list below, the names of 
required properties appear in <strong>bold</strong>. Any other properties (not 
in bold) are considered optional. The table also indicates any default valu
 es, and whether a property supports the <a 
href="../../html/expression-language-guide.html">NiFi Expression 
Language</a>.</p><table id="properties"><tr><th>Name</th><th>Default 
Value</th><th>Allowable Values</th><th>Description</th></tr><tr><td 
id="name"><strong>Database Connection Pooling Service</strong></td><td 
id="default-value"></td><td id="allowable-values"><strong>Controller Service 
API: </strong><br/>DBCPService<br/><strong>Implementations: </strong><br/><a 
href="../org.apache.nifi.dbcp.DBCPConnectionPool/index.html">DBCPConnectionPool</a><br/><a
 
href="../org.apache.nifi.dbcp.hive.HiveConnectionPool/index.html">HiveConnectionPool</a></td><td
 id="description">The Controller Service that is used to obtain connection to 
database</td></tr><tr><td id="name">SQL select query</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
SQL select query to execute. The query can be empty, a constant value, or built 
from attributes using Expression Language
 . If this property is specified, it will be used regardless of the content of 
incoming flowfiles. If this property is empty, the content of the incoming flow 
file is expected to contain a valid SQL select query, to be issued by the 
processor to the database. Note that Expression Language is not evaluated for 
flow file contents.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Max Wait Time</strong></td><td 
id="default-value">0 seconds</td><td id="allowable-values"></td><td 
id="description">The maximum amount of time allowed for a running SQL select 
query  , zero means there is no limit. Max time less than 1 second will be 
equal to zero.</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>Successfully
 created FlowFile from SQL query result 
set.</td></tr><tr><td>failure</td><td>SQL query execution failed. Incoming 
FlowFile will be penalized and routed to this rela
 tionship</td></tr></table><h3>Reads Attributes: </h3>None specified.<h3>Writes 
Attributes: </h3><table 
id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>executesql.row.count</td><td>Contains
 the number of rows returned in the select query</td></tr></table></body></html>
\ No newline at end of file
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>ExecuteSQL</title><link rel="stylesheet" 
href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Execute provided 
SQL select query. Query result will be converted to Avro format. Streaming is 
used so arbitrarily large result sets are supported. This processor can be 
scheduled to run on a timer, or cron expression, using the standard scheduling 
methods, or it can be triggered by an incoming FlowFile. If it is triggered by 
an incoming FlowFile, then attributes of that FlowFile will be available when 
evaluating the select query. FlowFile attribute 'executesql.row.count' 
indicates how many rows were selected.</p><h3>Tags: </h3><p>sql, select, jdbc, 
query, database</p><h3>Properties: </h3><p>In the list below, the names of 
required properties appear in <strong>bold</strong>. Any other properties (not 
in bold) are considered optional. The table also indicates any default valu
 es, and whether a property supports the <a 
href="../../html/expression-language-guide.html">NiFi Expression 
Language</a>.</p><table id="properties"><tr><th>Name</th><th>Default 
Value</th><th>Allowable Values</th><th>Description</th></tr><tr><td 
id="name"><strong>Database Connection Pooling Service</strong></td><td 
id="default-value"></td><td id="allowable-values"><strong>Controller Service 
API: </strong><br/>DBCPService<br/><strong>Implementation:</strong><br/><a 
href="../org.apache.nifi.dbcp.DBCPConnectionPool/index.html">DBCPConnectionPool</a></td><td
 id="description">The Controller Service that is used to obtain connection to 
database</td></tr><tr><td id="name">SQL select query</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
SQL select query to execute. The query can be empty, a constant value, or built 
from attributes using Expression Language. If this property is specified, it 
will be used regardless of the content of incoming flowfiles. 
 If this property is empty, the content of the incoming flow file is expected 
to contain a valid SQL select query, to be issued by the processor to the 
database. Note that Expression Language is not evaluated for flow file 
contents.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Max Wait Time</strong></td><td 
id="default-value">0 seconds</td><td id="allowable-values"></td><td 
id="description">The maximum amount of time allowed for a running SQL select 
query  , zero means there is no limit. Max time less than 1 second will be 
equal to zero.</td></tr><tr><td id="name"><strong>Normalize Table/Column 
Names</strong></td><td id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Whether to change non-Avro-compatible characters in column 
names to Avro-compatible characters. For example, colons and periods will be 
changed to underscores in order to build a valid Avro record.</td></tr></t
 able><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>Successfully
 created FlowFile from SQL query result 
set.</td></tr><tr><td>failure</td><td>SQL query execution failed. Incoming 
FlowFile will be penalized and routed to this 
relationship</td></tr></table><h3>Reads Attributes: </h3>None 
specified.<h3>Writes Attributes: </h3><table 
id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>executesql.row.count</td><td>Contains
 the number of rows returned in the select query</td></tr></table><h3>State 
management: </h3>This processor has no state management.<h3>Restricted: 
</h3></body></html>
\ No newline at end of file

Modified: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ExecuteStreamCommand/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ExecuteStreamCommand/index.html?rev=1771896&r1=1771895&r2=1771896&view=diff
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ExecuteStreamCommand/index.html
 (original)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ExecuteStreamCommand/index.html
 Tue Nov 29 12:33:21 2016
@@ -1 +1 @@
-<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>ExecuteStreamCommand</title><link 
rel="stylesheet" href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Executes an 
external command on the contents of a flow file, and creates a new flow file 
with the results of the command.</p><h3>Tags: </h3><p>command execution, 
command, stream, execute</p><h3>Properties: </h3><p>In the list below, the 
names of required properties appear in <strong>bold</strong>. Any other 
properties (not in bold) are considered optional. The table also indicates any 
default values, and whether a property supports the <a 
href="../../html/expression-language-guide.html">NiFi Expression 
Language</a>.</p><table id="properties"><tr><th>Name</th><th>Default 
Value</th><th>Allowable Values</th><th>Description</th></tr><tr><td 
id="name">Command Arguments</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The arguments to s
 upply to the executable delimited by the ';' character.<br/><strong>Supports 
Expression Language: true</strong></td></tr><tr><td id="name"><strong>Command 
Path</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Specifies the command to be 
executed; if just the name of an executable is provided, it must be in the 
user's environment PATH.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Ignore STDIN</td><td 
id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">If true, the contents of the incoming flowfile will not be 
passed to the executing command</td></tr><tr><td id="name">Working 
Directory</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">The directory to use as the current working directory when 
executing the command<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Arg
 ument Delimiter</strong></td><td id="default-value">;</td><td 
id="allowable-values"></td><td id="description">Delimiter to use to separate 
arguments for a command [default: ;]. Must be a single 
character</td></tr><tr><td id="name">Output Destination Attribute</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">If 
set, the output of the stream command will be put into an attribute of the 
original FlowFile instead of a separate FlowFile. There will no longer be a 
relationship for 'output stream'. The value of this property will be the key 
for the output attribute.</td></tr><tr><td id="name">Max Attribute 
Length</td><td id="default-value">256</td><td id="allowable-values"></td><td 
id="description">If routing the output of the stream command to an attribute, 
the number of characters put to the attribute value will be at most this 
amount. This is important because attributes are held in memory and large 
attributes will quickly cause out of memory issues. I
 f the output goes longer than this value, it will truncated to fit. Consider 
making this smaller if able.</td></tr></table><h3>Dynamic Properties: 
</h3><p>Dynamic Properties allow the user to specify both the name and value of 
a property.<table 
id="dynamic-properties"><tr><th>Name</th><th>Value</th><th>Description</th></tr><tr><td
 id="name">An environment variable name</td><td id="value">An environment 
variable value</td><td>These environment variables are passed to the process 
spawned by this Processor</td></tr></table></p><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>output 
stream</td><td>The destination path for the flow file created from the 
command's output</td></tr><tr><td>original</td><td>FlowFiles that were 
successfully processed</td></tr></table><h3>Reads Attributes: </h3>None 
specified.<h3>Writes Attributes: </h3><table 
id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>execution.command</td><td>Th
 e name of the command 
executed</td></tr><tr><td>execution.command.args</td><td>The semi-colon 
delimited list of arguments</td></tr><tr><td>execution.status</td><td>The exit 
status code returned from executing the 
command</td></tr><tr><td>execution.error</td><td>Any error messages returned 
from executing the command</td></tr></table></body></html>
\ No newline at end of file
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>ExecuteStreamCommand</title><link 
rel="stylesheet" href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Executes an 
external command on the contents of a flow file, and creates a new flow file 
with the results of the command.</p><h3>Tags: </h3><p>command execution, 
command, stream, execute, restricted</p><h3>Properties: </h3><p>In the list 
below, the names of required properties appear in <strong>bold</strong>. Any 
other properties (not in bold) are considered optional. The table also 
indicates any default values, and whether a property supports the <a 
href="../../html/expression-language-guide.html">NiFi Expression 
Language</a>.</p><table id="properties"><tr><th>Name</th><th>Default 
Value</th><th>Allowable Values</th><th>Description</th></tr><tr><td 
id="name">Command Arguments</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The ar
 guments to supply to the executable delimited by the ';' 
character.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Command Path</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Specifies the command to be executed; if just the name of an 
executable is provided, it must be in the user's environment 
PATH.<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td 
id="name">Ignore STDIN</td><td id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">If true, the contents of the incoming flowfile will not be 
passed to the executing command</td></tr><tr><td id="name">Working 
Directory</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">The directory to use as the current working directory when 
executing the command<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"
 ><strong>Argument Delimiter</strong></td><td id="default-value">;</td><td 
 >id="allowable-values"></td><td id="description">Delimiter to use to separate 
 >arguments for a command [default: ;]. Must be a single 
 >character</td></tr><tr><td id="name">Output Destination Attribute</td><td 
 >id="default-value"></td><td id="allowable-values"></td><td 
 >id="description">If set, the output of the stream command will be put into an 
 >attribute of the original FlowFile instead of a separate FlowFile. There will 
 >no longer be a relationship for 'output stream'. The value of this property 
 >will be the key for the output attribute.</td></tr><tr><td id="name">Max 
 >Attribute Length</td><td id="default-value">256</td><td 
 >id="allowable-values"></td><td id="description">If routing the output of the 
 >stream command to an attribute, the number of characters put to the attribute 
 >value will be at most this amount. This is important because attributes are 
 >held in memory and large attributes will quickly cause out of memo
 ry issues. If the output goes longer than this value, it will truncated to 
fit. Consider making this smaller if able.</td></tr></table><h3>Dynamic 
Properties: </h3><p>Dynamic Properties allow the user to specify both the name 
and value of a property.<table 
id="dynamic-properties"><tr><th>Name</th><th>Value</th><th>Description</th></tr><tr><td
 id="name">An environment variable name</td><td id="value">An environment 
variable value</td><td>These environment variables are passed to the process 
spawned by this Processor</td></tr></table></p><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>output 
stream</td><td>The destination path for the flow file created from the 
command's output</td></tr><tr><td>original</td><td>FlowFiles that were 
successfully processed</td></tr></table><h3>Reads Attributes: </h3>None 
specified.<h3>Writes Attributes: </h3><table 
id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>execution.comman
 d</td><td>The name of the command 
executed</td></tr><tr><td>execution.command.args</td><td>The semi-colon 
delimited list of arguments</td></tr><tr><td>execution.status</td><td>The exit 
status code returned from executing the 
command</td></tr><tr><td>execution.error</td><td>Any error messages returned 
from executing the command</td></tr></table><h3>State management: </h3>This 
processor has no state management.<h3>Restricted: </h3><td>Provides operator 
the ability to execute arbitrary code assuming all permissions that NiFi 
has.</td></body></html>
\ No newline at end of file



Reply via email to