Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-0-10-nar/1.6.0/org.apache.nifi.processors.kafka.pubsub.ConsumeKafkaRecord_0_10/additionalDetails.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-0-10-nar/1.6.0/org.apache.nifi.processors.kafka.pubsub.ConsumeKafkaRecord_0_10/additionalDetails.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-0-10-nar/1.6.0/org.apache.nifi.processors.kafka.pubsub.ConsumeKafkaRecord_0_10/additionalDetails.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-0-10-nar/1.6.0/org.apache.nifi.processors.kafka.pubsub.ConsumeKafkaRecord_0_10/additionalDetails.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1,142 @@
+<!DOCTYPE html>
+<html lang="en">
+    <!--
+      Licensed to the Apache Software Foundation (ASF) under one or more
+      contributor license agreements.  See the NOTICE file distributed with
+      this work for additional information regarding copyright ownership.
+      The ASF licenses this file to You under the Apache License, Version 2.0
+      (the "License"); you may not use this file except in compliance with
+      the License.  You may obtain a copy of the License at
+          http://www.apache.org/licenses/LICENSE-2.0
+      Unless required by applicable law or agreed to in writing, software
+      distributed under the License is distributed on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+      See the License for the specific language governing permissions and
+      limitations under the License.
+    -->
+    <head>
+        <meta charset="utf-8" />
+        <title>ConsumeKafka</title>
+        <link rel="stylesheet" href="../../../../../css/component-usage.css" 
type="text/css" />
+    </head>
+
+    <body>
+        <!-- Processor Documentation 
================================================== -->
+        <h2>Description:</h2>
+        <p>
+            This Processor polls <a href="http://kafka.apache.org/";>Apache 
Kafka</a>
+            for data using KafkaConsumer API available with Kafka 0.10.x. When 
a message is received 
+            from Kafka, the message will be deserialized using the configured 
Record Reader, and then
+            written to a FlowFile by serializing the message with the 
configured Record Writer.
+        </p>
+        <h2>Security Configuration:</h2>
+        <p>
+            The Security Protocol property allows the user to specify the 
protocol for communicating
+            with the Kafka broker. The following sections describe each of the 
protocols in further detail.
+        </p>
+        <h3>PLAINTEXT</h3>
+        <p>
+            This option provides an unsecured connection to the broker, with 
no client authentication and no encryption.
+            In order to use this option the broker must be configured with a 
listener of the form:
+        <pre>
+    PLAINTEXT://host.name:port
+            </pre>
+        </p>
+        <h3>SSL</h3>
+        <p>
+            This option provides an encrypted connection to the broker, with 
optional client authentication. In order
+            to use this option the broker must be configured with a listener 
of the form:
+        <pre>
+    SSL://host.name:port
+            </pre>
+        In addition, the processor must have an SSL Context Service selected.
+        </p>
+        <p>
+            If the broker specifies ssl.client.auth=none, or does not specify 
ssl.client.auth, then the client will
+            not be required to present a certificate. In this case, the SSL 
Context Service selected may specify only
+            a truststore containing the public key of the certificate 
authority used to sign the broker's key.
+        </p>
+        <p>
+            If the broker specifies ssl.client.auth=required then the client 
will be required to present a certificate.
+            In this case, the SSL Context Service must also specify a keystore 
containing a client key, in addition to
+            a truststore as described above.
+        </p>
+        <h3>SASL_PLAINTEXT</h3>
+        <p>
+            This option uses SASL with a PLAINTEXT transport layer to 
authenticate to the broker. In order to use this
+            option the broker must be configured with a listener of the form:
+        <pre>
+    SASL_PLAINTEXT://host.name:port
+            </pre>
+        In addition, the Kerberos Service Name must be specified in the 
processor.
+        </p>
+        <h4>SASL_PLAINTEXT - GSSAPI</h4>
+        <p>
+            If the SASL mechanism is GSSAPI, then the client must provide a 
JAAS configuration to authenticate. The
+            JAAS configuration can be provided by specifying the 
java.security.auth.login.config system property in
+            NiFi's bootstrap.conf, such as:
+        <pre>
+    
java.arg.16=-Djava.security.auth.login.config=/path/to/kafka_client_jaas.conf
+            </pre>
+        </p>
+        <p>
+            An example of the JAAS config file would be the following:
+        <pre>
+    KafkaClient {
+        com.sun.security.auth.module.Krb5LoginModule required
+        useKeyTab=true
+        storeKey=true
+        keyTab="/path/to/nifi.keytab"
+        serviceName="kafka"
+        principal="n...@yourrealm.com";
+    };
+            </pre>
+        <b>NOTE:</b> The serviceName in the JAAS file must match the Kerberos 
Service Name in the processor.
+        </p>
+        <p>
+            Alternatively, starting with Apache NiFi 1.2.0 which uses the 
Kafka 0.10.2 client, the JAAS
+            configuration when using GSSAPI can be provided by specifying the 
Kerberos Principal and Kerberos Keytab
+            directly in the processor properties. This will dynamically create 
a JAAS configuration like above, and
+            will take precedence over the java.security.auth.login.config 
system property.
+        </p>
+        <h4>SASL_PLAINTEXT - PLAIN</h4>
+        <p>
+            If the SASL mechanism is PLAIN, then client must provide a JAAS 
configuration to authenticate, but
+            the JAAS configuration must use Kafka's PlainLoginModule. An 
example of the JAAS config file would
+            be the following:
+        <pre>
+    KafkaClient {
+      org.apache.kafka.common.security.plain.PlainLoginModule required
+      username="nifi"
+      password="nifi-password";
+    };
+            </pre>
+        </p>
+        <p>
+            <b>NOTE:</b> It is not recommended to use a SASL mechanism of 
PLAIN with SASL_PLAINTEXT, as it would transmit
+            the username and password unencrypted.
+        </p>
+        <p>
+            <b>NOTE:</b> Using the PlainLoginModule will cause it be 
registered in the JVM's static list of Providers, making
+            it visible to components in other NARs that may access the 
providers. There is currently a known issue
+            where Kafka processors using the PlainLoginModule will cause HDFS 
processors with Keberos to no longer work.
+        </p>
+        <h3>SASL_SSL</h3>
+        <p>
+            This option uses SASL with an SSL/TLS transport layer to 
authenticate to the broker. In order to use this
+            option the broker must be configured with a listener of the form:
+        <pre>
+    SASL_SSL://host.name:port
+            </pre>
+        </p>
+        <p>
+            See the SASL_PLAINTEXT section for a description of how to provide 
the proper JAAS configuration
+            depending on the SASL mechanism (GSSAPI or PLAIN).
+        </p>
+        <p>
+            See the SSL section for a description of how to configure the SSL 
Context Service based on the
+            ssl.client.auth property.
+        </p>
+
+    </body>
+</html>

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-0-10-nar/1.6.0/org.apache.nifi.processors.kafka.pubsub.ConsumeKafkaRecord_0_10/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-0-10-nar/1.6.0/org.apache.nifi.processors.kafka.pubsub.ConsumeKafkaRecord_0_10/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-0-10-nar/1.6.0/org.apache.nifi.processors.kafka.pubsub.ConsumeKafkaRecord_0_10/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-0-10-nar/1.6.0/org.apache.nifi.processors.kafka.pubsub.ConsumeKafkaRecord_0_10/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>ConsumeKafkaRecord_0_10</title><link 
rel="stylesheet" href="../../../../../css/component-usage.css" 
type="text/css"></link></head><script type="text/javascript">window.onload = 
function(){if(self==top) { document.getElementById('nameHeader').style.display 
= "inherit"; } }</script><body><h1 id="nameHeader" style="display: 
none;">ConsumeKafkaRecord_0_10</h1><h2>Description: </h2><p>Consumes messages 
from Apache Kafka specifically built against the Kafka 0.10.x Consumer API. The 
complementary NiFi processor for sending messages is PublishKafkaRecord_0_10. 
Please note that, at this time, the Processor assumes that all records that are 
retrieved from a given partition have the same schema. If any of the Kafka 
messages are pulled but cannot be parsed or written with the configured Record 
Reader or Record Writer, the contents of the message will be written to a 
separate FlowFile, and that FlowFile will be transferred 
 to the 'parse.failure' relationship. Otherwise, each FlowFile is sent to the 
'success' relationship and may contain many individual messages within the 
single FlowFile. A 'record.count' attribute is added to indicate how many 
records are contained in the FlowFile.</p><p><a 
href="additionalDetails.html">Additional Details...</a></p><h3>Tags: 
</h3><p>Kafka, Get, Record, csv, avro, json, Ingest, Ingress, Topic, PubSub, 
Consume, 0.10.x</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>Kafka Brokers</strong></td><td 
id="default-value">localhost:9092</td><td id=
 "allowable-values"></td><td id="description">A comma-separated list of known 
Kafka Brokers in the format &lt;host&gt;:&lt;port&gt;<br/><strong>Supports 
Expression Language: true</strong></td></tr><tr><td id="name"><strong>Topic 
Name(s)</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The name of the Kafka Topic(s) 
to pull from. More than one can be supplied if comma 
separated.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Topic Name 
Format</strong></td><td id="default-value">names</td><td 
id="allowable-values"><ul><li>names <img 
src="../../../../../html/images/iconInfo.png" alt="Topic is a full topic name 
or comma separated list of names" title="Topic is a full topic name or comma 
separated list of names"></img></li><li>pattern <img 
src="../../../../../html/images/iconInfo.png" alt="Topic is a regex using the 
Java Pattern syntax" title="Topic is a regex using the Java Pattern 
syntax"></img></li>
 </ul></td><td id="description">Specifies whether the Topic(s) provided are a 
comma separated list of names or a single regular expression</td></tr><tr><td 
id="name"><strong>Record Reader</strong></td><td id="default-value"></td><td 
id="allowable-values"><strong>Controller Service API: 
</strong><br/>RecordReaderFactory<br/><strong>Implementations: </strong><a 
href="../../../nifi-record-serialization-services-nar/1.6.0/org.apache.nifi.avro.AvroReader/index.html">AvroReader</a><br/><a
 
href="../../../nifi-scripting-nar/1.6.0/org.apache.nifi.record.script.ScriptedReader/index.html">ScriptedReader</a><br/><a
 
href="../../../nifi-record-serialization-services-nar/1.6.0/org.apache.nifi.json.JsonPathReader/index.html">JsonPathReader</a><br/><a
 
href="../../../nifi-record-serialization-services-nar/1.6.0/org.apache.nifi.grok.GrokReader/index.html">GrokReader</a><br/><a
 
href="../../../nifi-record-serialization-services-nar/1.6.0/org.apache.nifi.csv.CSVReader/index.html">CSVReader</a><br/><a
 href
 
="../../../nifi-record-serialization-services-nar/1.6.0/org.apache.nifi.json.JsonTreeReader/index.html">JsonTreeReader</a></td><td
 id="description">The Record Reader to use for incoming 
FlowFiles</td></tr><tr><td id="name"><strong>Record Writer</strong></td><td 
id="default-value"></td><td id="allowable-values"><strong>Controller Service 
API: </strong><br/>RecordSetWriterFactory<br/><strong>Implementations: 
</strong><a 
href="../../../nifi-record-serialization-services-nar/1.6.0/org.apache.nifi.json.JsonRecordSetWriter/index.html">JsonRecordSetWriter</a><br/><a
 
href="../../../nifi-record-serialization-services-nar/1.6.0/org.apache.nifi.avro.AvroRecordSetWriter/index.html">AvroRecordSetWriter</a><br/><a
 
href="../../../nifi-scripting-nar/1.6.0/org.apache.nifi.record.script.ScriptedRecordSetWriter/index.html">ScriptedRecordSetWriter</a><br/><a
 
href="../../../nifi-record-serialization-services-nar/1.6.0/org.apache.nifi.text.FreeFormTextRecordSetWriter/index.html">FreeFormTextRecordSetWrit
 er</a><br/><a 
href="../../../nifi-record-serialization-services-nar/1.6.0/org.apache.nifi.csv.CSVRecordSetWriter/index.html">CSVRecordSetWriter</a></td><td
 id="description">The Record Writer to use in order to serialize the data 
before sending to Kafka</td></tr><tr><td id="name"><strong>Security 
Protocol</strong></td><td id="default-value">PLAINTEXT</td><td 
id="allowable-values"><ul><li>PLAINTEXT <img 
src="../../../../../html/images/iconInfo.png" alt="PLAINTEXT" 
title="PLAINTEXT"></img></li><li>SSL <img 
src="../../../../../html/images/iconInfo.png" alt="SSL" 
title="SSL"></img></li><li>SASL_PLAINTEXT <img 
src="../../../../../html/images/iconInfo.png" alt="SASL_PLAINTEXT" 
title="SASL_PLAINTEXT"></img></li><li>SASL_SSL <img 
src="../../../../../html/images/iconInfo.png" alt="SASL_SSL" 
title="SASL_SSL"></img></li></ul></td><td id="description">Protocol used to 
communicate with brokers. Corresponds to Kafka's 'security.protocol' 
property.</td></tr><tr><td id="name">Kerberos Credentials Se
 rvice</td><td id="default-value"></td><td 
id="allowable-values"><strong>Controller Service API: 
</strong><br/>KerberosCredentialsService<br/><strong>Implementation: 
</strong><a 
href="../../../nifi-kerberos-credentials-service-nar/1.6.0/org.apache.nifi.kerberos.KeytabCredentialsService/index.html">KeytabCredentialsService</a></td><td
 id="description">Specifies the Kerberos Credentials Controller Service that 
should be used for authenticating with Kerberos</td></tr><tr><td 
id="name">Kerberos Service Name</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The Kerberos principal name 
that Kafka runs as. This can be defined either in Kafka's JAAS config or in 
Kafka's config. Corresponds to Kafka's 'security.protocol' property.It is 
ignored unless one of the SASL options of the &lt;Security Protocol&gt; are 
selected.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Kerberos Principal</td><td 
id="default-value"></td><td id=
 "allowable-values"></td><td id="description">The Kerberos principal that will 
be used to connect to brokers. If not set, it is expected to set a JAAS 
configuration file in the JVM properties defined in the bootstrap.conf file. 
This principal will be set into 'sasl.jaas.config' Kafka's 
property.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Kerberos Keytab</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
Kerberos keytab that will be used to connect to brokers. If not set, it is 
expected to set a JAAS configuration file in the JVM properties defined in the 
bootstrap.conf file. This principal will be set into 'sasl.jaas.config' Kafka's 
property.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">SSL Context Service</td><td 
id="default-value"></td><td id="allowable-values"><strong>Controller Service 
API: </strong><br/>SSLContextService<br/><strong>Implementations: </strong><a 
href
 
="../../../nifi-ssl-context-service-nar/1.6.0/org.apache.nifi.ssl.StandardSSLContextService/index.html">StandardSSLContextService</a><br/><a
 
href="../../../nifi-ssl-context-service-nar/1.6.0/org.apache.nifi.ssl.StandardRestrictedSSLContextService/index.html">StandardRestrictedSSLContextService</a></td><td
 id="description">Specifies the SSL Context Service to use for communicating 
with Kafka.</td></tr><tr><td id="name"><strong>Group ID</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">A 
Group ID is used to identify consumers that are within the same consumer group. 
Corresponds to Kafka's 'group.id' property.</td></tr><tr><td 
id="name"><strong>Offset Reset</strong></td><td 
id="default-value">latest</td><td id="allowable-values"><ul><li>earliest <img 
src="../../../../../html/images/iconInfo.png" alt="Automatically reset the 
offset to the earliest offset" title="Automatically reset the offset to the 
earliest offset"></img></li><li>latest <img s
 rc="../../../../../html/images/iconInfo.png" alt="Automatically reset the 
offset to the latest offset" title="Automatically reset the offset to the 
latest offset"></img></li><li>none <img 
src="../../../../../html/images/iconInfo.png" alt="Throw exception to the 
consumer if no previous offset is found for the consumer's group" title="Throw 
exception to the consumer if no previous offset is found for the consumer's 
group"></img></li></ul></td><td id="description">Allows you to manage the 
condition when there is no initial offset in Kafka or if the current offset 
does not exist any more on the server (e.g. because that data has been 
deleted). Corresponds to Kafka's 'auto.offset.reset' property.</td></tr><tr><td 
id="name">Max Poll Records</td><td id="default-value">10000</td><td 
id="allowable-values"></td><td id="description">Specifies the maximum number of 
records Kafka should return in a single poll.</td></tr><tr><td id="name">Max 
Uncommitted Time</td><td id="default-value">1 secs</td
 ><td id="allowable-values"></td><td id="description">Specifies the maximum 
 >amount of time allowed to pass before offsets must be committed. This value 
 >impacts how often offsets will be committed.  Committing offsets less often 
 >increases throughput but also increases the window of potential data 
 >duplication in the event of a rebalance or JVM restart between commits.  This 
 >value is also related to maximum poll records and the use of a message 
 >demarcator.  When using a message demarcator we can have far more uncommitted 
 >messages than when we're not as there is much less for us to keep track of in 
 >memory.</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">The name of a Kafka configuration property.</td><td id="value">The 
 >value of a given Kafka configuration property.</td><td>These properties will 
 >be adde
 d on the Kafka configuration after loading any provided configuration 
properties. In the event a dynamic property represents a property that was 
already set, its value will be ignored and WARN message logged. For the list of 
available Kafka properties please refer to: 
http://kafka.apache.org/documentation.html#configuration. 
</td></tr></table></p><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>FlowFiles
 received from Kafka.  Depending on demarcation strategy it is a flow file per 
message or a bundle of messages grouped by topic and 
partition.</td></tr><tr><td>parse.failure</td><td>If a message from Kafka 
cannot be parsed using the configured Record Reader, the contents of the 
message will be routed to this Relationship as its own individual 
FlowFile.</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>r
 ecord.count</td><td>The number of records 
received</td></tr><tr><td>mime.type</td><td>The MIME Type that is provided by 
the configured Record Writer</td></tr><tr><td>kafka.partition</td><td>The 
partition of the topic the records are 
from</td></tr><tr><td>kafka.topic</td><td>The topic records are 
from</td></tr></table><h3>State management: </h3>This component does not store 
state.<h3>Restricted: </h3>This component is not restricted.<h3>Input 
requirement: </h3>This component does not allow an incoming 
relationship.<h3>System Resource Considerations:</h3>None specified.<h3>See 
Also:</h3><p><a 
href="../org.apache.nifi.processors.kafka.pubsub.ConsumeKafka_0_10/index.html">ConsumeKafka_0_10</a>,
 <a 
href="../org.apache.nifi.processors.kafka.pubsub.PublishKafka_0_10/index.html">PublishKafka_0_10</a>,
 <a 
href="../org.apache.nifi.processors.kafka.pubsub.PublishKafkaRecord_0_10/index.html">PublishKafkaRecord_0_10</a></p></body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-0-10-nar/1.6.0/org.apache.nifi.processors.kafka.pubsub.ConsumeKafka_0_10/additionalDetails.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-0-10-nar/1.6.0/org.apache.nifi.processors.kafka.pubsub.ConsumeKafka_0_10/additionalDetails.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-0-10-nar/1.6.0/org.apache.nifi.processors.kafka.pubsub.ConsumeKafka_0_10/additionalDetails.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-0-10-nar/1.6.0/org.apache.nifi.processors.kafka.pubsub.ConsumeKafka_0_10/additionalDetails.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1,142 @@
+<!DOCTYPE html>
+<html lang="en">
+    <!--
+      Licensed to the Apache Software Foundation (ASF) under one or more
+      contributor license agreements.  See the NOTICE file distributed with
+      this work for additional information regarding copyright ownership.
+      The ASF licenses this file to You under the Apache License, Version 2.0
+      (the "License"); you may not use this file except in compliance with
+      the License.  You may obtain a copy of the License at
+          http://www.apache.org/licenses/LICENSE-2.0
+      Unless required by applicable law or agreed to in writing, software
+      distributed under the License is distributed on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+      See the License for the specific language governing permissions and
+      limitations under the License.
+    -->
+    <head>
+        <meta charset="utf-8" />
+        <title>ConsumeKafka</title>
+        <link rel="stylesheet" href="../../../../../css/component-usage.css" 
type="text/css" />
+    </head>
+
+    <body>
+        <!-- Processor Documentation 
================================================== -->
+        <h2>Description:</h2>
+        <p>
+            This Processor polls <a href="http://kafka.apache.org/";>Apache 
Kafka</a>
+            for data using KafkaConsumer API available with Kafka 0.10.x. When 
a message is received 
+            from Kafka, this Processor emits a FlowFile where the content of 
the FlowFile is the value 
+            of the Kafka message.
+        </p>
+        <h2>Security Configuration:</h2>
+        <p>
+            The Security Protocol property allows the user to specify the 
protocol for communicating
+            with the Kafka broker. The following sections describe each of the 
protocols in further detail.
+        </p>
+        <h3>PLAINTEXT</h3>
+        <p>
+            This option provides an unsecured connection to the broker, with 
no client authentication and no encryption.
+            In order to use this option the broker must be configured with a 
listener of the form:
+        <pre>
+    PLAINTEXT://host.name:port
+            </pre>
+        </p>
+        <h3>SSL</h3>
+        <p>
+            This option provides an encrypted connection to the broker, with 
optional client authentication. In order
+            to use this option the broker must be configured with a listener 
of the form:
+        <pre>
+    SSL://host.name:port
+            </pre>
+        In addition, the processor must have an SSL Context Service selected.
+        </p>
+        <p>
+            If the broker specifies ssl.client.auth=none, or does not specify 
ssl.client.auth, then the client will
+            not be required to present a certificate. In this case, the SSL 
Context Service selected may specify only
+            a truststore containing the public key of the certificate 
authority used to sign the broker's key.
+        </p>
+        <p>
+            If the broker specifies ssl.client.auth=required then the client 
will be required to present a certificate.
+            In this case, the SSL Context Service must also specify a keystore 
containing a client key, in addition to
+            a truststore as described above.
+        </p>
+        <h3>SASL_PLAINTEXT</h3>
+        <p>
+            This option uses SASL with a PLAINTEXT transport layer to 
authenticate to the broker. In order to use this
+            option the broker must be configured with a listener of the form:
+        <pre>
+    SASL_PLAINTEXT://host.name:port
+            </pre>
+        In addition, the Kerberos Service Name must be specified in the 
processor.
+        </p>
+        <h4>SASL_PLAINTEXT - GSSAPI</h4>
+        <p>
+            If the SASL mechanism is GSSAPI, then the client must provide a 
JAAS configuration to authenticate. The
+            JAAS configuration can be provided by specifying the 
java.security.auth.login.config system property in
+            NiFi's bootstrap.conf, such as:
+        <pre>
+    
java.arg.16=-Djava.security.auth.login.config=/path/to/kafka_client_jaas.conf
+            </pre>
+        </p>
+        <p>
+            An example of the JAAS config file would be the following:
+        <pre>
+    KafkaClient {
+        com.sun.security.auth.module.Krb5LoginModule required
+        useKeyTab=true
+        storeKey=true
+        keyTab="/path/to/nifi.keytab"
+        serviceName="kafka"
+        principal="n...@yourrealm.com";
+    };
+            </pre>
+        <b>NOTE:</b> The serviceName in the JAAS file must match the Kerberos 
Service Name in the processor.
+        </p>
+        <p>
+            Alternatively, starting with Apache NiFi 1.2.0 which uses the 
Kafka 0.10.2 client, the JAAS
+            configuration when using GSSAPI can be provided by specifying the 
Kerberos Principal and Kerberos Keytab
+            directly in the processor properties. This will dynamically create 
a JAAS configuration like above, and
+            will take precedence over the java.security.auth.login.config 
system property.
+        </p>
+        <h4>SASL_PLAINTEXT - PLAIN</h4>
+        <p>
+            If the SASL mechanism is PLAIN, then client must provide a JAAS 
configuration to authenticate, but
+            the JAAS configuration must use Kafka's PlainLoginModule. An 
example of the JAAS config file would
+            be the following:
+        <pre>
+    KafkaClient {
+      org.apache.kafka.common.security.plain.PlainLoginModule required
+      username="nifi"
+      password="nifi-password";
+    };
+            </pre>
+        </p>
+        <p>
+            <b>NOTE:</b> It is not recommended to use a SASL mechanism of 
PLAIN with SASL_PLAINTEXT, as it would transmit
+            the username and password unencrypted.
+        </p>
+        <p>
+            <b>NOTE:</b> Using the PlainLoginModule will cause it be 
registered in the JVM's static list of Providers, making
+            it visible to components in other NARs that may access the 
providers. There is currently a known issue
+            where Kafka processors using the PlainLoginModule will cause HDFS 
processors with Keberos to no longer work.
+        </p>
+        <h3>SASL_SSL</h3>
+        <p>
+            This option uses SASL with an SSL/TLS transport layer to 
authenticate to the broker. In order to use this
+            option the broker must be configured with a listener of the form:
+        <pre>
+    SASL_SSL://host.name:port
+            </pre>
+        </p>
+        <p>
+            See the SASL_PLAINTEXT section for a description of how to provide 
the proper JAAS configuration
+            depending on the SASL mechanism (GSSAPI or PLAIN).
+        </p>
+        <p>
+            See the SSL section for a description of how to configure the SSL 
Context Service based on the
+            ssl.client.auth property.
+        </p>
+
+    </body>
+</html>

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-0-10-nar/1.6.0/org.apache.nifi.processors.kafka.pubsub.ConsumeKafka_0_10/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-0-10-nar/1.6.0/org.apache.nifi.processors.kafka.pubsub.ConsumeKafka_0_10/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-0-10-nar/1.6.0/org.apache.nifi.processors.kafka.pubsub.ConsumeKafka_0_10/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-0-10-nar/1.6.0/org.apache.nifi.processors.kafka.pubsub.ConsumeKafka_0_10/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>ConsumeKafka_0_10</title><link rel="stylesheet" 
href="../../../../../css/component-usage.css" 
type="text/css"></link></head><script type="text/javascript">window.onload = 
function(){if(self==top) { document.getElementById('nameHeader').style.display 
= "inherit"; } }</script><body><h1 id="nameHeader" style="display: 
none;">ConsumeKafka_0_10</h1><h2>Description: </h2><p>Consumes messages from 
Apache Kafka specifically built against the Kafka 0.10.x Consumer API. The 
complementary NiFi processor for sending messages is 
PublishKafka_0_10.</p><p><a href="additionalDetails.html">Additional 
Details...</a></p><h3>Tags: </h3><p>Kafka, Get, Ingest, Ingress, Topic, PubSub, 
Consume, 0.10.x</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 proper
 ty 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>Kafka Brokers</strong></td><td 
id="default-value">localhost:9092</td><td id="allowable-values"></td><td 
id="description">A comma-separated list of known Kafka Brokers in the format 
&lt;host&gt;:&lt;port&gt;<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Security 
Protocol</strong></td><td id="default-value">PLAINTEXT</td><td 
id="allowable-values"><ul><li>PLAINTEXT <img 
src="../../../../../html/images/iconInfo.png" alt="PLAINTEXT" 
title="PLAINTEXT"></img></li><li>SSL <img 
src="../../../../../html/images/iconInfo.png" alt="SSL" 
title="SSL"></img></li><li>SASL_PLAINTEXT <img 
src="../../../../../html/images/iconInfo.png" alt="SASL_PLAINTEXT" 
title="SASL_PLAINTEXT"></img></li><li>SASL_SSL <img src="../
 ../../../../html/images/iconInfo.png" alt="SASL_SSL" 
title="SASL_SSL"></img></li></ul></td><td id="description">Protocol used to 
communicate with brokers. Corresponds to Kafka's 'security.protocol' 
property.</td></tr><tr><td id="name">Kerberos Service Name</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
Kerberos principal name that Kafka runs as. This can be defined either in 
Kafka's JAAS config or in Kafka's config. Corresponds to Kafka's 
'security.protocol' property.It is ignored unless one of the SASL options of 
the &lt;Security Protocol&gt; are selected.<br/><strong>Supports Expression 
Language: true</strong></td></tr><tr><td id="name">Kerberos Credentials 
Service</td><td id="default-value"></td><td 
id="allowable-values"><strong>Controller Service API: 
</strong><br/>KerberosCredentialsService<br/><strong>Implementation: 
</strong><a 
href="../../../nifi-kerberos-credentials-service-nar/1.6.0/org.apache.nifi.kerberos.KeytabCredentialsService/
 index.html">KeytabCredentialsService</a></td><td id="description">Specifies 
the Kerberos Credentials Controller Service that should be used for 
authenticating with Kerberos</td></tr><tr><td id="name">Kerberos 
Principal</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">The Kerberos principal that will be used to connect to 
brokers. If not set, it is expected to set a JAAS configuration file in the JVM 
properties defined in the bootstrap.conf file. This principal will be set into 
'sasl.jaas.config' Kafka's property.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Kerberos Keytab</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
Kerberos keytab that will be used to connect to brokers. If not set, it is 
expected to set a JAAS configuration file in the JVM properties defined in the 
bootstrap.conf file. This principal will be set into 'sasl.jaas.config' Kafka's 
property.<br/><strong>
 Supports Expression Language: true</strong></td></tr><tr><td id="name">SSL 
Context Service</td><td id="default-value"></td><td 
id="allowable-values"><strong>Controller Service API: 
</strong><br/>SSLContextService<br/><strong>Implementations: </strong><a 
href="../../../nifi-ssl-context-service-nar/1.6.0/org.apache.nifi.ssl.StandardSSLContextService/index.html">StandardSSLContextService</a><br/><a
 
href="../../../nifi-ssl-context-service-nar/1.6.0/org.apache.nifi.ssl.StandardRestrictedSSLContextService/index.html">StandardRestrictedSSLContextService</a></td><td
 id="description">Specifies the SSL Context Service to use for communicating 
with Kafka.</td></tr><tr><td id="name"><strong>Topic Name(s)</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
name of the Kafka Topic(s) to pull from. More than one can be supplied if comma 
separated.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Topic Name Forma
 t</strong></td><td id="default-value">names</td><td 
id="allowable-values"><ul><li>names <img 
src="../../../../../html/images/iconInfo.png" alt="Topic is a full topic name 
or comma separated list of names" title="Topic is a full topic name or comma 
separated list of names"></img></li><li>pattern <img 
src="../../../../../html/images/iconInfo.png" alt="Topic is a regex using the 
Java Pattern syntax" title="Topic is a regex using the Java Pattern 
syntax"></img></li></ul></td><td id="description">Specifies whether the 
Topic(s) provided are a comma separated list of names or a single regular 
expression</td></tr><tr><td id="name"><strong>Group ID</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">A 
Group ID is used to identify consumers that are within the same consumer group. 
Corresponds to Kafka's 'group.id' property.</td></tr><tr><td 
id="name"><strong>Offset Reset</strong></td><td 
id="default-value">latest</td><td id="allowable-values"><ul><li>e
 arliest <img src="../../../../../html/images/iconInfo.png" alt="Automatically 
reset the offset to the earliest offset" title="Automatically reset the offset 
to the earliest offset"></img></li><li>latest <img 
src="../../../../../html/images/iconInfo.png" alt="Automatically reset the 
offset to the latest offset" title="Automatically reset the offset to the 
latest offset"></img></li><li>none <img 
src="../../../../../html/images/iconInfo.png" alt="Throw exception to the 
consumer if no previous offset is found for the consumer's group" title="Throw 
exception to the consumer if no previous offset is found for the consumer's 
group"></img></li></ul></td><td id="description">Allows you to manage the 
condition when there is no initial offset in Kafka or if the current offset 
does not exist any more on the server (e.g. because that data has been 
deleted). Corresponds to Kafka's 'auto.offset.reset' property.</td></tr><tr><td 
id="name"><strong>Key Attribute Encoding</strong></td><td id="default-
 value">utf-8</td><td id="allowable-values"><ul><li>UTF-8 Encoded <img 
src="../../../../../html/images/iconInfo.png" alt="The key is interpreted as a 
UTF-8 Encoded string." title="The key is interpreted as a UTF-8 Encoded 
string."></img></li><li>Hex Encoded <img 
src="../../../../../html/images/iconInfo.png" alt="The key is interpreted as 
arbitrary binary data and is encoded using hexadecimal characters with 
uppercase letters" title="The key is interpreted as arbitrary binary data and 
is encoded using hexadecimal characters with uppercase 
letters"></img></li></ul></td><td id="description">FlowFiles that are emitted 
have an attribute named 'kafka.key'. This property dictates how the value of 
the attribute should be encoded.</td></tr><tr><td id="name">Message 
Demarcator</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">Since KafkaConsumer receives messages in batches, you have an 
option to output FlowFiles which contains all Kafka messages in a single b
 atch for a given topic and partition and this property allows you to provide a 
string (interpreted as UTF-8) to use for demarcating apart multiple Kafka 
messages. This is an optional property and if not provided each Kafka message 
received will result in a single FlowFile which  time it is triggered. To enter 
special character such as 'new line' use CTRL+Enter or Shift+Enter depending on 
the OS<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td 
id="name">Max Poll Records</td><td id="default-value">10000</td><td 
id="allowable-values"></td><td id="description">Specifies the maximum number of 
records Kafka should return in a single poll.</td></tr><tr><td id="name">Max 
Uncommitted Time</td><td id="default-value">1 secs</td><td 
id="allowable-values"></td><td id="description">Specifies the maximum amount of 
time allowed to pass before offsets must be committed. This value impacts how 
often offsets will be committed.  Committing offsets less often increases 
throughput
  but also increases the window of potential data duplication in the event of a 
rebalance or JVM restart between commits.  This value is also related to 
maximum poll records and the use of a message demarcator.  When using a message 
demarcator we can have far more uncommitted messages than when we're not as 
there is much less for us to keep track of in 
memory.</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">The name of a Kafka configuration property.</td><td id="value">The 
value of a given Kafka configuration property.</td><td>These properties will be 
added on the Kafka configuration after loading any provided configuration 
properties. In the event a dynamic property represents a property that was 
already set, its value will be ignored and WARN message logged. For the list of 
available Kafka proper
 ties please refer to: 
http://kafka.apache.org/documentation.html#configuration. 
</td></tr></table></p><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>FlowFiles
 received from Kafka.  Depending on demarcation strategy it is a flow file per 
message or a bundle of messages grouped by topic and 
partition.</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>kafka.count</td><td>The
 number of messages written if more than 
one</td></tr><tr><td>kafka.key</td><td>The key of message if present and if 
single message. How the key is encoded depends on the value of the 'Key 
Attribute Encoding' property.</td></tr><tr><td>kafka.offset</td><td>The offset 
of the message in the partition of the 
topic.</td></tr><tr><td>kafka.partition</td><td>The partition of the topic the 
message or message bundle is from</td></tr><tr><td>
 kafka.topic</td><td>The topic the message or message bundle is 
from</td></tr></table><h3>State management: </h3>This component does not store 
state.<h3>Restricted: </h3>This component is not restricted.<h3>Input 
requirement: </h3>This component does not allow an incoming 
relationship.<h3>System Resource Considerations:</h3>None 
specified.</body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-0-10-nar/1.6.0/org.apache.nifi.processors.kafka.pubsub.PublishKafkaRecord_0_10/additionalDetails.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-0-10-nar/1.6.0/org.apache.nifi.processors.kafka.pubsub.PublishKafkaRecord_0_10/additionalDetails.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-0-10-nar/1.6.0/org.apache.nifi.processors.kafka.pubsub.PublishKafkaRecord_0_10/additionalDetails.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-0-10-nar/1.6.0/org.apache.nifi.processors.kafka.pubsub.PublishKafkaRecord_0_10/additionalDetails.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1,143 @@
+<!DOCTYPE html>
+<html lang="en">
+    <!--
+      Licensed to the Apache Software Foundation (ASF) under one or more
+      contributor license agreements.  See the NOTICE file distributed with
+      this work for additional information regarding copyright ownership.
+      The ASF licenses this file to You under the Apache License, Version 2.0
+      (the "License"); you may not use this file except in compliance with
+      the License.  You may obtain a copy of the License at
+          http://www.apache.org/licenses/LICENSE-2.0
+      Unless required by applicable law or agreed to in writing, software
+      distributed under the License is distributed on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+      See the License for the specific language governing permissions and
+      limitations under the License.
+    -->
+    <head>
+        <meta charset="utf-8" />
+        <title>PublishKafka</title>
+        <link rel="stylesheet" href="../../../../../css/component-usage.css" 
type="text/css" />
+    </head>
+
+    <body>
+        <!-- Processor Documentation 
================================================== -->
+        <h2>Description:</h2>
+        <p>
+            This Processor puts the contents of a FlowFile to a Topic in
+            <a href="http://kafka.apache.org/";>Apache Kafka</a> using 
KafkaProducer API available
+            with Kafka 0.10.x API. The contents of the incoming FlowFile will 
be read using the
+            configured Record Reader. Each record will then be serialized 
using the configured
+            Record Writer, and this serialized form will be the content of a 
Kafka message.
+            This message is optionally assigned a key by using the &lt;Kafka 
Key&gt; Property.
+        </p>
+        <h2>Security Configuration:</h2>
+        <p>
+            The Security Protocol property allows the user to specify the 
protocol for communicating
+            with the Kafka broker. The following sections describe each of the 
protocols in further detail.
+        </p>
+        <h3>PLAINTEXT</h3>
+        <p>
+            This option provides an unsecured connection to the broker, with 
no client authentication and no encryption.
+            In order to use this option the broker must be configured with a 
listener of the form:
+            <pre>
+    PLAINTEXT://host.name:port
+            </pre>
+        </p>
+        <h3>SSL</h3>
+        <p>
+            This option provides an encrypted connection to the broker, with 
optional client authentication. In order
+            to use this option the broker must be configured with a listener 
of the form:
+            <pre>
+    SSL://host.name:port
+            </pre>
+            In addition, the processor must have an SSL Context Service 
selected.
+        </p>
+        <p>
+            If the broker specifies ssl.client.auth=none, or does not specify 
ssl.client.auth, then the client will
+            not be required to present a certificate. In this case, the SSL 
Context Service selected may specify only
+            a truststore containing the public key of the certificate 
authority used to sign the broker's key.
+        </p>
+        <p>
+            If the broker specifies ssl.client.auth=required then the client 
will be required to present a certificate.
+            In this case, the SSL Context Service must also specify a keystore 
containing a client key, in addition to
+            a truststore as described above.
+        </p>
+        <h3>SASL_PLAINTEXT</h3>
+        <p>
+            This option uses SASL with a PLAINTEXT transport layer to 
authenticate to the broker. In order to use this
+            option the broker must be configured with a listener of the form:
+            <pre>
+    SASL_PLAINTEXT://host.name:port
+            </pre>
+            In addition, the Kerberos Service Name must be specified in the 
processor.
+        </p>
+        <h4>SASL_PLAINTEXT - GSSAPI</h4>
+        <p>
+            If the SASL mechanism is GSSAPI, then the client must provide a 
JAAS configuration to authenticate. The
+            JAAS configuration can be provided by specifying the 
java.security.auth.login.config system property in
+            NiFi's bootstrap.conf, such as:
+            <pre>
+    
java.arg.16=-Djava.security.auth.login.config=/path/to/kafka_client_jaas.conf
+            </pre>
+        </p>
+        <p>
+            An example of the JAAS config file would be the following:
+            <pre>
+    KafkaClient {
+        com.sun.security.auth.module.Krb5LoginModule required
+        useKeyTab=true
+        storeKey=true
+        keyTab="/path/to/nifi.keytab"
+        serviceName="kafka"
+        principal="n...@yourrealm.com";
+    };
+            </pre>
+        <b>NOTE:</b> The serviceName in the JAAS file must match the Kerberos 
Service Name in the processor.
+        </p>
+        <p>
+            Alternatively, starting with Apache NiFi 1.2.0 which uses the 
Kafka 0.10.2 client, the JAAS
+            configuration when using GSSAPI can be provided by specifying the 
Kerberos Principal and Kerberos Keytab
+            directly in the processor properties. This will dynamically create 
a JAAS configuration like above, and
+            will take precedence over the java.security.auth.login.config 
system property.
+        </p>
+        <h4>SASL_PLAINTEXT - PLAIN</h4>
+        <p>
+            If the SASL mechanism is PLAIN, then client must provide a JAAS 
configuration to authenticate, but
+            the JAAS configuration must use Kafka's PlainLoginModule. An 
example of the JAAS config file would
+            be the following:
+            <pre>
+    KafkaClient {
+      org.apache.kafka.common.security.plain.PlainLoginModule required
+      username="nifi"
+      password="nifi-password";
+    };
+            </pre>
+        </p>
+        <p>
+            <b>NOTE:</b> It is not recommended to use a SASL mechanism of 
PLAIN with SASL_PLAINTEXT, as it would transmit
+            the username and password unencrypted.
+        </p>
+        <p>
+            <b>NOTE:</b> Using the PlainLoginModule will cause it be 
registered in the JVM's static list of Providers, making
+            it visible to components in other NARs that may access the 
providers. There is currently a known issue
+            where Kafka processors using the PlainLoginModule will cause HDFS 
processors with Keberos to no longer work.
+        </p>
+        <h3>SASL_SSL</h3>
+        <p>
+            This option uses SASL with an SSL/TLS transport layer to 
authenticate to the broker. In order to use this
+            option the broker must be configured with a listener of the form:
+            <pre>
+    SASL_SSL://host.name:port
+            </pre>
+        </p>
+        <p>
+            See the SASL_PLAINTEXT section for a description of how to provide 
the proper JAAS configuration
+            depending on the SASL mechanism (GSSAPI or PLAIN).
+        </p>
+        <p>
+            See the SSL section for a description of how to configure the SSL 
Context Service based on the
+            ssl.client.auth property.
+        </p>
+    </body>
+</html>

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-0-10-nar/1.6.0/org.apache.nifi.processors.kafka.pubsub.PublishKafkaRecord_0_10/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-0-10-nar/1.6.0/org.apache.nifi.processors.kafka.pubsub.PublishKafkaRecord_0_10/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-0-10-nar/1.6.0/org.apache.nifi.processors.kafka.pubsub.PublishKafkaRecord_0_10/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-0-10-nar/1.6.0/org.apache.nifi.processors.kafka.pubsub.PublishKafkaRecord_0_10/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>PublishKafkaRecord_0_10</title><link 
rel="stylesheet" href="../../../../../css/component-usage.css" 
type="text/css"></link></head><script type="text/javascript">window.onload = 
function(){if(self==top) { document.getElementById('nameHeader').style.display 
= "inherit"; } }</script><body><h1 id="nameHeader" style="display: 
none;">PublishKafkaRecord_0_10</h1><h2>Description: </h2><p>Sends the contents 
of a FlowFile as individual records to Apache Kafka using the Kafka 0.10.x 
Producer API. The contents of the FlowFile are expected to be record-oriented 
data that can be read by the configured Record Reader. The complementary NiFi 
processor for fetching messages is ConsumeKafka_0_10_Record.</p><p><a 
href="additionalDetails.html">Additional Details...</a></p><h3>Tags: 
</h3><p>Apache, Kafka, Record, csv, json, avro, logs, Put, Send, Message, 
PubSub, 0.10.x</p><h3>Properties: </h3><p>In the list below, the names of requ
 ired 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>Kafka Brokers</strong></td><td 
id="default-value">localhost:9092</td><td id="allowable-values"></td><td 
id="description">A comma-separated list of known Kafka Brokers in the format 
&lt;host&gt;:&lt;port&gt;<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Topic Name</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
name of the Kafka Topic to publish to.<br/><strong>Supports Expression 
Language: true</strong></td></tr><tr><td id="name"><strong>Record 
Reader</strong></td><td id="defa
 ult-value"></td><td id="allowable-values"><strong>Controller Service API: 
</strong><br/>RecordReaderFactory<br/><strong>Implementations: </strong><a 
href="../../../nifi-record-serialization-services-nar/1.6.0/org.apache.nifi.avro.AvroReader/index.html">AvroReader</a><br/><a
 
href="../../../nifi-scripting-nar/1.6.0/org.apache.nifi.record.script.ScriptedReader/index.html">ScriptedReader</a><br/><a
 
href="../../../nifi-record-serialization-services-nar/1.6.0/org.apache.nifi.json.JsonPathReader/index.html">JsonPathReader</a><br/><a
 
href="../../../nifi-record-serialization-services-nar/1.6.0/org.apache.nifi.grok.GrokReader/index.html">GrokReader</a><br/><a
 
href="../../../nifi-record-serialization-services-nar/1.6.0/org.apache.nifi.csv.CSVReader/index.html">CSVReader</a><br/><a
 
href="../../../nifi-record-serialization-services-nar/1.6.0/org.apache.nifi.json.JsonTreeReader/index.html">JsonTreeReader</a></td><td
 id="description">The Record Reader to use for incoming 
FlowFiles</td></tr><tr><td
  id="name"><strong>Record Writer</strong></td><td id="default-value"></td><td 
id="allowable-values"><strong>Controller Service API: 
</strong><br/>RecordSetWriterFactory<br/><strong>Implementations: </strong><a 
href="../../../nifi-record-serialization-services-nar/1.6.0/org.apache.nifi.json.JsonRecordSetWriter/index.html">JsonRecordSetWriter</a><br/><a
 
href="../../../nifi-record-serialization-services-nar/1.6.0/org.apache.nifi.avro.AvroRecordSetWriter/index.html">AvroRecordSetWriter</a><br/><a
 
href="../../../nifi-scripting-nar/1.6.0/org.apache.nifi.record.script.ScriptedRecordSetWriter/index.html">ScriptedRecordSetWriter</a><br/><a
 
href="../../../nifi-record-serialization-services-nar/1.6.0/org.apache.nifi.text.FreeFormTextRecordSetWriter/index.html">FreeFormTextRecordSetWriter</a><br/><a
 
href="../../../nifi-record-serialization-services-nar/1.6.0/org.apache.nifi.csv.CSVRecordSetWriter/index.html">CSVRecordSetWriter</a></td><td
 id="description">The Record Writer to use in order to se
 rialize the data before sending to Kafka</td></tr><tr><td 
id="name"><strong>Security Protocol</strong></td><td 
id="default-value">PLAINTEXT</td><td id="allowable-values"><ul><li>PLAINTEXT 
<img src="../../../../../html/images/iconInfo.png" alt="PLAINTEXT" 
title="PLAINTEXT"></img></li><li>SSL <img 
src="../../../../../html/images/iconInfo.png" alt="SSL" 
title="SSL"></img></li><li>SASL_PLAINTEXT <img 
src="../../../../../html/images/iconInfo.png" alt="SASL_PLAINTEXT" 
title="SASL_PLAINTEXT"></img></li><li>SASL_SSL <img 
src="../../../../../html/images/iconInfo.png" alt="SASL_SSL" 
title="SASL_SSL"></img></li></ul></td><td id="description">Protocol used to 
communicate with brokers. Corresponds to Kafka's 'security.protocol' 
property.</td></tr><tr><td id="name">Kerberos Credentials Service</td><td 
id="default-value"></td><td id="allowable-values"><strong>Controller Service 
API: </strong><br/>KerberosCredentialsService<br/><strong>Implementation: 
</strong><a href="../../../nifi-kerberos-creden
 
tials-service-nar/1.6.0/org.apache.nifi.kerberos.KeytabCredentialsService/index.html">KeytabCredentialsService</a></td><td
 id="description">Specifies the Kerberos Credentials Controller Service that 
should be used for authenticating with Kerberos</td></tr><tr><td 
id="name">Kerberos Service Name</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The Kerberos principal name 
that Kafka runs as. This can be defined either in Kafka's JAAS config or in 
Kafka's config. Corresponds to Kafka's 'security.protocol' property.It is 
ignored unless one of the SASL options of the &lt;Security Protocol&gt; are 
selected.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Kerberos Principal</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
Kerberos principal that will be used to connect to brokers. If not set, it is 
expected to set a JAAS configuration file in the JVM properties defined in the 
bootst
 rap.conf file. This principal will be set into 'sasl.jaas.config' Kafka's 
property.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Kerberos Keytab</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
Kerberos keytab that will be used to connect to brokers. If not set, it is 
expected to set a JAAS configuration file in the JVM properties defined in the 
bootstrap.conf file. This principal will be set into 'sasl.jaas.config' Kafka's 
property.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">SSL Context Service</td><td 
id="default-value"></td><td id="allowable-values"><strong>Controller Service 
API: </strong><br/>SSLContextService<br/><strong>Implementations: </strong><a 
href="../../../nifi-ssl-context-service-nar/1.6.0/org.apache.nifi.ssl.StandardSSLContextService/index.html">StandardSSLContextService</a><br/><a
 href="../../../nifi-ssl-context-service-nar/1.6.0/org.apache.nifi.ssl.S
 
tandardRestrictedSSLContextService/index.html">StandardRestrictedSSLContextService</a></td><td
 id="description">Specifies the SSL Context Service to use for communicating 
with Kafka.</td></tr><tr><td id="name"><strong>Delivery 
Guarantee</strong></td><td id="default-value">0</td><td 
id="allowable-values"><ul><li>Best Effort <img 
src="../../../../../html/images/iconInfo.png" alt="FlowFile will be routed to 
success after successfully writing the content to a Kafka node, without waiting 
for a response. This provides the best performance but may result in data 
loss." title="FlowFile will be routed to success after successfully writing the 
content to a Kafka node, without waiting for a response. This provides the best 
performance but may result in data loss."></img></li><li>Guarantee Single Node 
Delivery <img src="../../../../../html/images/iconInfo.png" alt="FlowFile will 
be routed to success if the message is received by a single Kafka node, whether 
or not it is replicated. This is fast
 er than &lt;Guarantee Replicated Delivery&gt; but can result in data loss if a 
Kafka node crashes" title="FlowFile will be routed to success if the message is 
received by a single Kafka node, whether or not it is replicated. This is 
faster than &lt;Guarantee Replicated Delivery&gt; but can result in data loss 
if a Kafka node crashes"></img></li><li>Guarantee Replicated Delivery <img 
src="../../../../../html/images/iconInfo.png" alt="FlowFile will be routed to 
failure unless the message is replicated to the appropriate number of Kafka 
Nodes according to the Topic configuration" title="FlowFile will be routed to 
failure unless the message is replicated to the appropriate number of Kafka 
Nodes according to the Topic configuration"></img></li></ul></td><td 
id="description">Specifies the requirement for guaranteeing that a message is 
sent to Kafka. Corresponds to Kafka's 'acks' property.</td></tr><tr><td 
id="name">Message Key Field</td><td id="default-value"></td><td 
id="allowable-values
 "></td><td id="description">The name of a field in the Input Records that 
should be used as the Key for the Kafka message.<br/><strong>Supports 
Expression Language: true</strong></td></tr><tr><td id="name"><strong>Max 
Request Size</strong></td><td id="default-value">1 MB</td><td 
id="allowable-values"></td><td id="description">The maximum size of a request 
in bytes. Corresponds to Kafka's 'max.request.size' property and defaults to 1 
MB (1048576).</td></tr><tr><td id="name"><strong>Acknowledgment Wait 
Time</strong></td><td id="default-value">5 secs</td><td 
id="allowable-values"></td><td id="description">After sending a message to 
Kafka, this indicates the amount of time that we are willing to wait for a 
response from Kafka. If Kafka does not acknowledge the message within this time 
period, the FlowFile will be routed to 'failure'.</td></tr><tr><td 
id="name"><strong>Max Metadata Wait Time</strong></td><td id="default-value">5 
sec</td><td id="allowable-values"></td><td id="description"
 >The amount of time publisher will wait to obtain metadata or wait for the 
 >buffer to flush during the 'send' call before failing the entire 'send' call. 
 >Corresponds to Kafka's 'max.block.ms' property<br/><strong>Supports 
 >Expression Language: true</strong></td></tr><tr><td id="name">Partitioner 
 >class</td><td 
 >id="default-value">org.apache.kafka.clients.producer.internals.DefaultPartitioner</td><td
 > id="allowable-values"><ul><li>RoundRobinPartitioner <img 
 >src="../../../../../html/images/iconInfo.png" alt="Messages will be assigned 
 >partitions in a round-robin fashion, sending the first message to Partition 
 >1, the next Partition to Partition 2, and so on, wrapping as necessary." 
 >title="Messages will be assigned partitions in a round-robin fashion, sending 
 >the first message to Partition 1, the next Partition to Partition 2, and so 
 >on, wrapping as necessary."></img></li><li>DefaultPartitioner <img 
 >src="../../../../../html/images/iconInfo.png" alt="Messages will be assigned 
 >to random partiti
 ons." title="Messages will be assigned to random 
partitions."></img></li></ul></td><td id="description">Specifies which class to 
use to compute a partition id for a message. Corresponds to Kafka's 
'partitioner.class' property.</td></tr><tr><td id="name"><strong>Compression 
Type</strong></td><td id="default-value">none</td><td 
id="allowable-values"><ul><li>none</li><li>gzip</li><li>snappy</li><li>lz4</li></ul></td><td
 id="description">This parameter allows you to specify the compression codec 
for all data generated by this producer.</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">The name of a Kafka configuration property.</td><td id="value">The 
value of a given Kafka configuration property.</td><td>These properties will be 
added on the Kafka configuration after loading any provided configuration p
 roperties. In the event a dynamic property represents a property that was 
already set, its value will be ignored and WARN message logged. For the list of 
available Kafka properties please refer to: 
http://kafka.apache.org/documentation.html#configuration. 
</td></tr></table></p><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>FlowFiles
 for which all content was sent to Kafka.</td></tr><tr><td>failure</td><td>Any 
FlowFile that cannot be sent to Kafka will be 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>msg.count</td><td>The
 number of messages that were sent to Kafka for this FlowFile. This attribute 
is added only to FlowFiles that are routed to 
success.</td></tr></table><h3>State management: </h3>This component does not 
store state.<h3>Restricted: </h3>This component is n
 ot restricted.<h3>Input requirement: </h3>This component requires an incoming 
relationship.<h3>System Resource Considerations:</h3>None specified.<h3>See 
Also:</h3><p><a 
href="../org.apache.nifi.processors.kafka.pubsub.PublishKafka_0_10/index.html">PublishKafka_0_10</a>,
 <a 
href="../org.apache.nifi.processors.kafka.pubsub.ConsumeKafka_0_10/index.html">ConsumeKafka_0_10</a>,
 <a 
href="../org.apache.nifi.processors.kafka.pubsub.ConsumeKafkaRecord_0_10/index.html">ConsumeKafkaRecord_0_10</a></p></body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-0-10-nar/1.6.0/org.apache.nifi.processors.kafka.pubsub.PublishKafka_0_10/additionalDetails.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-0-10-nar/1.6.0/org.apache.nifi.processors.kafka.pubsub.PublishKafka_0_10/additionalDetails.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-0-10-nar/1.6.0/org.apache.nifi.processors.kafka.pubsub.PublishKafka_0_10/additionalDetails.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-0-10-nar/1.6.0/org.apache.nifi.processors.kafka.pubsub.PublishKafka_0_10/additionalDetails.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1,155 @@
+<!DOCTYPE html>
+<html lang="en">
+    <!--
+      Licensed to the Apache Software Foundation (ASF) under one or more
+      contributor license agreements.  See the NOTICE file distributed with
+      this work for additional information regarding copyright ownership.
+      The ASF licenses this file to You under the Apache License, Version 2.0
+      (the "License"); you may not use this file except in compliance with
+      the License.  You may obtain a copy of the License at
+          http://www.apache.org/licenses/LICENSE-2.0
+      Unless required by applicable law or agreed to in writing, software
+      distributed under the License is distributed on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+      See the License for the specific language governing permissions and
+      limitations under the License.
+    -->
+    <head>
+        <meta charset="utf-8" />
+        <title>PublishKafka</title>
+        <link rel="stylesheet" href="../../../../../css/component-usage.css" 
type="text/css" />
+    </head>
+
+    <body>
+        <!-- Processor Documentation 
================================================== -->
+        <h2>Description:</h2>
+        <p>
+            This Processor puts the contents of a FlowFile to a Topic in
+            <a href="http://kafka.apache.org/";>Apache Kafka</a> using 
KafkaProducer API available
+            with Kafka 0.10.x API. The content of a FlowFile becomes the 
contents of a Kafka message.
+            This message is optionally assigned a key by using the &lt;Kafka 
Key&gt; Property.
+        </p>
+
+        <p>
+            The Processor allows the user to configure an optional Message 
Demarcator that
+            can be used to send many messages per FlowFile. For example, a 
<i>\n</i> could be used
+            to indicate that the contents of the FlowFile should be used to 
send one message
+            per line of text. It also supports multi-char demarcators (e.g., 
'my custom demarcator').
+            If the property is not set, the entire contents of the FlowFile
+            will be sent as a single message. When using the demarcator, if 
some messages are
+            successfully sent but other messages fail to send, the resulting 
FlowFile will be
+            considered a failed FlowFile and will have additional attributes 
to that effect.
+            One of such attributes is 'failed.last.idx' which indicates the 
index of the last message
+            that was successfully ACKed by Kafka. (if no demarcator is used 
the value of this index will be -1).
+            This will allow PublishKafka to only re-send un-ACKed messages on 
the next re-try.
+        </p>
+        <h2>Security Configuration:</h2>
+        <p>
+            The Security Protocol property allows the user to specify the 
protocol for communicating
+            with the Kafka broker. The following sections describe each of the 
protocols in further detail.
+        </p>
+        <h3>PLAINTEXT</h3>
+        <p>
+            This option provides an unsecured connection to the broker, with 
no client authentication and no encryption.
+            In order to use this option the broker must be configured with a 
listener of the form:
+            <pre>
+    PLAINTEXT://host.name:port
+            </pre>
+        </p>
+        <h3>SSL</h3>
+        <p>
+            This option provides an encrypted connection to the broker, with 
optional client authentication. In order
+            to use this option the broker must be configured with a listener 
of the form:
+            <pre>
+    SSL://host.name:port
+            </pre>
+            In addition, the processor must have an SSL Context Service 
selected.
+        </p>
+        <p>
+            If the broker specifies ssl.client.auth=none, or does not specify 
ssl.client.auth, then the client will
+            not be required to present a certificate. In this case, the SSL 
Context Service selected may specify only
+            a truststore containing the public key of the certificate 
authority used to sign the broker's key.
+        </p>
+        <p>
+            If the broker specifies ssl.client.auth=required then the client 
will be required to present a certificate.
+            In this case, the SSL Context Service must also specify a keystore 
containing a client key, in addition to
+            a truststore as described above.
+        </p>
+        <h3>SASL_PLAINTEXT</h3>
+        <p>
+            This option uses SASL with a PLAINTEXT transport layer to 
authenticate to the broker. In order to use this
+            option the broker must be configured with a listener of the form:
+            <pre>
+    SASL_PLAINTEXT://host.name:port
+            </pre>
+            In addition, the Kerberos Service Name must be specified in the 
processor.
+        </p>
+        <h4>SASL_PLAINTEXT - GSSAPI</h4>
+        <p>
+            If the SASL mechanism is GSSAPI, then the client must provide a 
JAAS configuration to authenticate. The
+            JAAS configuration can be provided by specifying the 
java.security.auth.login.config system property in
+            NiFi's bootstrap.conf, such as:
+            <pre>
+    
java.arg.16=-Djava.security.auth.login.config=/path/to/kafka_client_jaas.conf
+            </pre>
+        </p>
+        <p>
+            An example of the JAAS config file would be the following:
+            <pre>
+    KafkaClient {
+        com.sun.security.auth.module.Krb5LoginModule required
+        useKeyTab=true
+        storeKey=true
+        keyTab="/path/to/nifi.keytab"
+        serviceName="kafka"
+        principal="n...@yourrealm.com";
+    };
+            </pre>
+        <b>NOTE:</b> The serviceName in the JAAS file must match the Kerberos 
Service Name in the processor.
+        </p>
+        <p>
+            Alternatively, starting with Apache NiFi 1.2.0 which uses the 
Kafka 0.10.2 client, the JAAS
+            configuration when using GSSAPI can be provided by specifying the 
Kerberos Principal and Kerberos Keytab
+            directly in the processor properties. This will dynamically create 
a JAAS configuration like above, and
+            will take precedence over the java.security.auth.login.config 
system property.
+        </p>
+        <h4>SASL_PLAINTEXT - PLAIN</h4>
+        <p>
+            If the SASL mechanism is PLAIN, then client must provide a JAAS 
configuration to authenticate, but
+            the JAAS configuration must use Kafka's PlainLoginModule. An 
example of the JAAS config file would
+            be the following:
+            <pre>
+    KafkaClient {
+      org.apache.kafka.common.security.plain.PlainLoginModule required
+      username="nifi"
+      password="nifi-password";
+    };
+            </pre>
+        </p>
+        <p>
+            <b>NOTE:</b> It is not recommended to use a SASL mechanism of 
PLAIN with SASL_PLAINTEXT, as it would transmit
+            the username and password unencrypted.
+        </p>
+        <p>
+            <b>NOTE:</b> Using the PlainLoginModule will cause it be 
registered in the JVM's static list of Providers, making
+            it visible to components in other NARs that may access the 
providers. There is currently a known issue
+            where Kafka processors using the PlainLoginModule will cause HDFS 
processors with Keberos to no longer work.
+        </p>
+        <h3>SASL_SSL</h3>
+        <p>
+            This option uses SASL with an SSL/TLS transport layer to 
authenticate to the broker. In order to use this
+            option the broker must be configured with a listener of the form:
+            <pre>
+    SASL_SSL://host.name:port
+            </pre>
+        </p>
+        <p>
+            See the SASL_PLAINTEXT section for a description of how to provide 
the proper JAAS configuration
+            depending on the SASL mechanism (GSSAPI or PLAIN).
+        </p>
+        <p>
+            See the SSL section for a description of how to configure the SSL 
Context Service based on the
+            ssl.client.auth property.
+        </p>
+    </body>
+</html>

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-0-10-nar/1.6.0/org.apache.nifi.processors.kafka.pubsub.PublishKafka_0_10/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-0-10-nar/1.6.0/org.apache.nifi.processors.kafka.pubsub.PublishKafka_0_10/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-0-10-nar/1.6.0/org.apache.nifi.processors.kafka.pubsub.PublishKafka_0_10/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-0-10-nar/1.6.0/org.apache.nifi.processors.kafka.pubsub.PublishKafka_0_10/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>PublishKafka_0_10</title><link rel="stylesheet" 
href="../../../../../css/component-usage.css" 
type="text/css"></link></head><script type="text/javascript">window.onload = 
function(){if(self==top) { document.getElementById('nameHeader').style.display 
= "inherit"; } }</script><body><h1 id="nameHeader" style="display: 
none;">PublishKafka_0_10</h1><h2>Description: </h2><p>Sends the contents of a 
FlowFile as a message to Apache Kafka using the Kafka 0.10.x Producer API.The 
messages to send may be individual FlowFiles or may be delimited, using a 
user-specified delimiter, such as a new-line. The complementary NiFi processor 
for fetching messages is ConsumeKafka_0_10.</p><p><a 
href="additionalDetails.html">Additional Details...</a></p><h3>Tags: 
</h3><p>Apache, Kafka, Put, Send, Message, PubSub, 0.10.x</p><h3>Properties: 
</h3><p>In the list below, the names of required properties appear in 
<strong>bold</strong>. Any ot
 her 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>Kafka Brokers</strong></td><td 
id="default-value">localhost:9092</td><td id="allowable-values"></td><td 
id="description">A comma-separated list of known Kafka Brokers in the format 
&lt;host&gt;:&lt;port&gt;<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Security 
Protocol</strong></td><td id="default-value">PLAINTEXT</td><td 
id="allowable-values"><ul><li>PLAINTEXT <img 
src="../../../../../html/images/iconInfo.png" alt="PLAINTEXT" 
title="PLAINTEXT"></img></li><li>SSL <img 
src="../../../../../html/images/iconInfo.png" alt="SSL" 
title="SSL"></img></li><li>SASL_PLAINTEXT <img src="../
 ../../../../html/images/iconInfo.png" alt="SASL_PLAINTEXT" 
title="SASL_PLAINTEXT"></img></li><li>SASL_SSL <img 
src="../../../../../html/images/iconInfo.png" alt="SASL_SSL" 
title="SASL_SSL"></img></li></ul></td><td id="description">Protocol used to 
communicate with brokers. Corresponds to Kafka's 'security.protocol' 
property.</td></tr><tr><td id="name">Kerberos Service Name</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
Kerberos principal name that Kafka runs as. This can be defined either in 
Kafka's JAAS config or in Kafka's config. Corresponds to Kafka's 
'security.protocol' property.It is ignored unless one of the SASL options of 
the &lt;Security Protocol&gt; are selected.<br/><strong>Supports Expression 
Language: true</strong></td></tr><tr><td id="name">Kerberos Credentials 
Service</td><td id="default-value"></td><td 
id="allowable-values"><strong>Controller Service API: 
</strong><br/>KerberosCredentialsService<br/><strong>Implementation: </
 strong><a 
href="../../../nifi-kerberos-credentials-service-nar/1.6.0/org.apache.nifi.kerberos.KeytabCredentialsService/index.html">KeytabCredentialsService</a></td><td
 id="description">Specifies the Kerberos Credentials Controller Service that 
should be used for authenticating with Kerberos</td></tr><tr><td 
id="name">Kerberos Principal</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The Kerberos principal that 
will be used to connect to brokers. If not set, it is expected to set a JAAS 
configuration file in the JVM properties defined in the bootstrap.conf file. 
This principal will be set into 'sasl.jaas.config' Kafka's 
property.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Kerberos Keytab</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
Kerberos keytab that will be used to connect to brokers. If not set, it is 
expected to set a JAAS configuration file in the JVM propertie
 s defined in the bootstrap.conf file. This principal will be set into 
'sasl.jaas.config' Kafka's property.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">SSL Context Service</td><td 
id="default-value"></td><td id="allowable-values"><strong>Controller Service 
API: </strong><br/>SSLContextService<br/><strong>Implementations: </strong><a 
href="../../../nifi-ssl-context-service-nar/1.6.0/org.apache.nifi.ssl.StandardSSLContextService/index.html">StandardSSLContextService</a><br/><a
 
href="../../../nifi-ssl-context-service-nar/1.6.0/org.apache.nifi.ssl.StandardRestrictedSSLContextService/index.html">StandardRestrictedSSLContextService</a></td><td
 id="description">Specifies the SSL Context Service to use for communicating 
with Kafka.</td></tr><tr><td id="name"><strong>Topic Name</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
name of the Kafka Topic to publish to.<br/><strong>Supports Expression 
Language: t
 rue</strong></td></tr><tr><td id="name"><strong>Delivery 
Guarantee</strong></td><td id="default-value">0</td><td 
id="allowable-values"><ul><li>Best Effort <img 
src="../../../../../html/images/iconInfo.png" alt="FlowFile will be routed to 
success after successfully writing the content to a Kafka node, without waiting 
for a response. This provides the best performance but may result in data 
loss." title="FlowFile will be routed to success after successfully writing the 
content to a Kafka node, without waiting for a response. This provides the best 
performance but may result in data loss."></img></li><li>Guarantee Single Node 
Delivery <img src="../../../../../html/images/iconInfo.png" alt="FlowFile will 
be routed to success if the message is received by a single Kafka node, whether 
or not it is replicated. This is faster than &lt;Guarantee Replicated 
Delivery&gt; but can result in data loss if a Kafka node crashes" 
title="FlowFile will be routed to success if the message is received by
  a single Kafka node, whether or not it is replicated. This is faster than 
&lt;Guarantee Replicated Delivery&gt; but can result in data loss if a Kafka 
node crashes"></img></li><li>Guarantee Replicated Delivery <img 
src="../../../../../html/images/iconInfo.png" alt="FlowFile will be routed to 
failure unless the message is replicated to the appropriate number of Kafka 
Nodes according to the Topic configuration" title="FlowFile will be routed to 
failure unless the message is replicated to the appropriate number of Kafka 
Nodes according to the Topic configuration"></img></li></ul></td><td 
id="description">Specifies the requirement for guaranteeing that a message is 
sent to Kafka. Corresponds to Kafka's 'acks' property.</td></tr><tr><td 
id="name">Kafka Key</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The Key to use for the Message. 
If not specified, the flow file attribute 'kafka.key' is used as the message 
key, if it is present.Beware that setting
  Kafka key and demarcating at the same time may potentially lead to many Kafka 
messages with the same key.Normally this is not a problem as Kafka does not 
enforce or assume message and key uniqueness. Still, setting the demarcator and 
Kafka key at the same time poses a risk of data loss on Kafka. During a topic 
compaction on Kafka, messages will be deduplicated based on this 
key.<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td 
id="name"><strong>Key Attribute Encoding</strong></td><td 
id="default-value">utf-8</td><td id="allowable-values"><ul><li>UTF-8 Encoded 
<img src="../../../../../html/images/iconInfo.png" alt="The key is interpreted 
as a UTF-8 Encoded string." title="The key is interpreted as a UTF-8 Encoded 
string."></img></li><li>Hex Encoded <img 
src="../../../../../html/images/iconInfo.png" alt="The key is interpreted as 
arbitrary binary data that is encoded using hexadecimal characters with 
uppercase letters." title="The key is interpreted as arbitra
 ry binary data that is encoded using hexadecimal characters with uppercase 
letters."></img></li></ul></td><td id="description">FlowFiles that are emitted 
have an attribute named 'kafka.key'. This property dictates how the value of 
the attribute should be encoded.</td></tr><tr><td id="name">Message 
Demarcator</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">Specifies the string (interpreted as UTF-8) to use for 
demarcating multiple messages within a single FlowFile. If not specified, the 
entire content of the FlowFile will be used as a single message. If specified, 
the contents of the FlowFile will be split on this delimiter and each section 
sent as a separate Kafka message. To enter special character such as 'new line' 
use CTRL+Enter or Shift+Enter, depending on your OS.<br/><strong>Supports 
Expression Language: true</strong></td></tr><tr><td id="name"><strong>Max 
Request Size</strong></td><td id="default-value">1 MB</td><td 
id="allowable-values"><
 /td><td id="description">The maximum size of a request in bytes. Corresponds 
to Kafka's 'max.request.size' property and defaults to 1 MB 
(1048576).</td></tr><tr><td id="name"><strong>Acknowledgment Wait 
Time</strong></td><td id="default-value">5 secs</td><td 
id="allowable-values"></td><td id="description">After sending a message to 
Kafka, this indicates the amount of time that we are willing to wait for a 
response from Kafka. If Kafka does not acknowledge the message within this time 
period, the FlowFile will be routed to 'failure'.</td></tr><tr><td 
id="name"><strong>Max Metadata Wait Time</strong></td><td id="default-value">5 
sec</td><td id="allowable-values"></td><td id="description">The amount of time 
publisher will wait to obtain metadata or wait for the buffer to flush during 
the 'send' call before failing the entire 'send' call. Corresponds to Kafka's 
'max.block.ms' property<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Partitioner class</t
 d><td 
id="default-value">org.apache.kafka.clients.producer.internals.DefaultPartitioner</td><td
 id="allowable-values"><ul><li>RoundRobinPartitioner <img 
src="../../../../../html/images/iconInfo.png" alt="Messages will be assigned 
partitions in a round-robin fashion, sending the first message to Partition 1, 
the next Partition to Partition 2, and so on, wrapping as necessary." 
title="Messages will be assigned partitions in a round-robin fashion, sending 
the first message to Partition 1, the next Partition to Partition 2, and so on, 
wrapping as necessary."></img></li><li>DefaultPartitioner <img 
src="../../../../../html/images/iconInfo.png" alt="Messages will be assigned to 
random partitions." title="Messages will be assigned to random 
partitions."></img></li></ul></td><td id="description">Specifies which class to 
use to compute a partition id for a message. Corresponds to Kafka's 
'partitioner.class' property.</td></tr><tr><td id="name"><strong>Compression 
Type</strong></td><td id="def
 ault-value">none</td><td 
id="allowable-values"><ul><li>none</li><li>gzip</li><li>snappy</li><li>lz4</li></ul></td><td
 id="description">This parameter allows you to specify the compression codec 
for all data generated by this producer.</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">The name of a Kafka configuration property.</td><td id="value">The 
value of a given Kafka configuration property.</td><td>These properties will be 
added on the Kafka configuration after loading any provided configuration 
properties. In the event a dynamic property represents a property that was 
already set, its value will be ignored and WARN message logged. For the list of 
available Kafka properties please refer to: 
http://kafka.apache.org/documentation.html#configuration. 
</td></tr></table></p><h3>Relationships: </h3><
 table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>FlowFiles
 for which all content was sent to Kafka.</td></tr><tr><td>failure</td><td>Any 
FlowFile that cannot be sent to Kafka will be 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>msg.count</td><td>The
 number of messages that were sent to Kafka for this FlowFile. This attribute 
is added only to FlowFiles that are routed to success. If the &lt;Message 
Demarcator&gt; Property is not set, this will always be 1, but if the Property 
is set, it may be greater than 1.</td></tr></table><h3>State management: 
</h3>This component does not store state.<h3>Restricted: </h3>This component is 
not restricted.<h3>Input requirement: </h3>This component requires an incoming 
relationship.<h3>System Resource Considerations:</h3>None 
specified.</body></html>
\ No newline at end of file


Reply via email to