NIFI-4600: This closes #2312. Added nifi-kafka-1-0-nar and nifi-kafka-1-0-processors modules Signed-off-by: joewitt Project: http://git-wip-us.apache.org/repos/asf/nifi/repo Commit: http://git-wip-us.apache.org/repos/asf/nifi/commit/00b11e82 Tree: http://git-wip-us.apache.org/repos/asf/nifi/tree/00b11e82 Diff: http://git-wip-us.apache.org/repos/asf/nifi/diff/00b11e82 Branch: refs/heads/master Commit: 00b11e82b73eccf739b533814189e64d101fbfa7 Parents: 7b6aab7 Author: Mark Payne Authored: Sun Dec 3 14:36:10 2017 -0500 Committer: joewitt Committed: Mon Dec 4 16:51:59 2017 -0500 ---------------------------------------------------------------------- nifi-assembly/pom.xml | 5 + .../additionalDetails.html | 143 ---- .../additionalDetails.html | 143 ++++ .../additionalDetails.html | 143 ---- .../additionalDetails.html | 143 ++++ .../additionalDetails.html | 144 ---- .../additionalDetails.html | 144 ++++ .../additionalDetails.html | 156 ----- .../additionalDetails.html | 156 +++++ .../nifi-kafka-1-0-nar/pom.xml | 40 ++ .../src/main/resources/META-INF/LICENSE | 233 ++++++ .../src/main/resources/META-INF/NOTICE | 83 +++ .../nifi-kafka-1-0-processors/pom.xml | 92 +++ .../kafka/pubsub/ConsumeKafkaRecord_1_0.java | 395 +++++++++++ .../kafka/pubsub/ConsumeKafka_1_0.java | 386 ++++++++++ .../processors/kafka/pubsub/ConsumerLease.java | 701 +++++++++++++++++++ .../processors/kafka/pubsub/ConsumerPool.java | 372 ++++++++++ .../kafka/pubsub/InFlightMessageTracker.java | 175 +++++ .../kafka/pubsub/KafkaProcessorUtils.java | 332 +++++++++ .../processors/kafka/pubsub/Partitioners.java | 62 ++ .../kafka/pubsub/PublishKafkaRecord_1_0.java | 443 ++++++++++++ .../kafka/pubsub/PublishKafka_1_0.java | 458 ++++++++++++ .../processors/kafka/pubsub/PublishResult.java | 46 ++ .../processors/kafka/pubsub/PublisherLease.java | 264 +++++++ .../processors/kafka/pubsub/PublisherPool.java | 115 +++ .../org.apache.nifi.processor.Processor | 18 + .../additionalDetails.html | 143 ++++ .../additionalDetails.html | 143 ++++ .../additionalDetails.html | 144 ++++ .../additionalDetails.html | 156 +++++ .../kafka/pubsub/ConsumeKafkaTest.java | 218 ++++++ .../kafka/pubsub/ConsumerPoolTest.java | 233 ++++++ .../pubsub/TestConsumeKafkaRecord_1_0.java | 216 ++++++ .../pubsub/TestInFlightMessageTracker.java | 88 +++ .../kafka/pubsub/TestPublishKafka.java | 250 +++++++ .../pubsub/TestPublishKafkaRecord_1_0.java | 300 ++++++++ .../kafka/pubsub/TestPublisherLease.java | 190 +++++ .../kafka/pubsub/TestPublisherPool.java | 69 ++ .../nifi/processors/kafka/pubsub/TestUtils.java | 45 ++ .../kafka/pubsub/util/MockRecordParser.java | 105 +++ .../kafka/pubsub/util/MockRecordWriter.java | 128 ++++ .../processors/kafka/test/EmbeddedKafka.java | 226 ++++++ .../src/test/resources/log4j.properties | 21 + .../src/test/resources/server.properties | 121 ++++ .../src/test/resources/zookeeper.properties | 20 + nifi-nar-bundles/nifi-kafka-bundle/pom.xml | 8 + pom.xml | 6 + 47 files changed, 7636 insertions(+), 586 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/nifi/blob/00b11e82/nifi-assembly/pom.xml ---------------------------------------------------------------------- diff --git a/nifi-assembly/pom.xml b/nifi-assembly/pom.xml index b1ab989..ddcd6e8 100755 --- a/nifi-assembly/pom.xml +++ b/nifi-assembly/pom.xml @@ -198,6 +198,11 @@ language governing permissions and limitations under the License. --> org.apache.nifi + nifi-kafka-1-0-nar + nar + + + org.apache.nifi nifi-confluent-platform-nar nar http://git-wip-us.apache.org/repos/asf/nifi/blob/00b11e82/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-0-11-processors/src/main/resources/docs/org.apache.nifi.processors.kafka.pubsub.ConsumeKafkaRecord_0_10/additionalDetails.html ---------------------------------------------------------------------- diff --git a/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-0-11-processors/src/main/resources/docs/org.apache.nifi.processors.kafka.pubsub.ConsumeKafkaRecord_0_10/additionalDetails.html b/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-0-11-processors/src/main/resources/docs/org.apache.nifi.processors.kafka.pubsub.ConsumeKafkaRecord_0_10/additionalDetails.html deleted file mode 100644 index 018a289..0000000 --- a/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-0-11-processors/src/main/resources/docs/org.apache.nifi.processors.kafka.pubsub.ConsumeKafkaRecord_0_10/additionalDetails.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - - ConsumeKafka - - - - -

Description

-

- This Processor polls Apache Kafka - for data using KafkaConsumer API available with Kafka 0.11.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. -

- - -

Security Configuration:

-

- 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. -

-

PLAINTEXT

-

- 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: -

-    PLAINTEXT://host.name:port
-            
-

-

SSL

-

- 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: -

-    SSL://host.name:port
-            
- In addition, the processor must have an SSL Context Service selected. -

-

- 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. -

-

- 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. -

-

SASL_PLAINTEXT

-

- 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: -

-    SASL_PLAINTEXT://host.name:port
-            
- In addition, the Kerberos Service Name must be specified in the processor. -

-

SASL_PLAINTEXT - GSSAPI

-

- 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: -

-    java.arg.16=-Djava.security.auth.login.config=/path/to/kafka_client_jaas.conf
-            
-

-

- An example of the JAAS config file would be the following: -

-    KafkaClient {
-        com.sun.security.auth.module.Krb5LoginModule required
-        useKeyTab=true
-        storeKey=true
-        keyTab="/path/to/nifi.keytab"
-        serviceName="kafka"
-        principal="nifi@YOURREALM.COM";
-    };
-            
- NOTE: The serviceName in the JAAS file must match the Kerberos Service Name in the processor. -

-

- Alternatively, 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. -

-

SASL_PLAINTEXT - PLAIN

-

- 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: -

-    KafkaClient {
-      org.apache.kafka.common.security.plain.PlainLoginModule required
-      username="nifi"
-      password="nifi-password";
-    };
-            
-

-

- NOTE: It is not recommended to use a SASL mechanism of PLAIN with SASL_PLAINTEXT, as it would transmit - the username and password unencrypted. -

-

- NOTE: 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. -

-

SASL_SSL

-

- 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: -

-    SASL_SSL://host.name:port
-            
-

-

- See the SASL_PLAINTEXT section for a description of how to provide the proper JAAS configuration - depending on the SASL mechanism (GSSAPI or PLAIN). -

-

- See the SSL section for a description of how to configure the SSL Context Service based on the - ssl.client.auth property. -

- - - http://git-wip-us.apache.org/repos/asf/nifi/blob/00b11e82/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-0-11-processors/src/main/resources/docs/org.apache.nifi.processors.kafka.pubsub.ConsumeKafkaRecord_0_11/additionalDetails.html ---------------------------------------------------------------------- diff --git a/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-0-11-processors/src/main/resources/docs/org.apache.nifi.processors.kafka.pubsub.ConsumeKafkaRecord_0_11/additionalDetails.html b/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-0-11-processors/src/main/resources/docs/org.apache.nifi.processors.kafka.pubsub.ConsumeKafkaRecord_0_11/additionalDetails.html new file mode 100644 index 0000000..018a289 --- /dev/null +++ b/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-0-11-processors/src/main/resources/docs/org.apache.nifi.processors.kafka.pubsub.ConsumeKafkaRecord_0_11/additionalDetails.html @@ -0,0 +1,143 @@ + + + + + + ConsumeKafka + + + + +

Description

+

+ This Processor polls Apache Kafka + for data using KafkaConsumer API available with Kafka 0.11.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. +

+ + +

Security Configuration:

+

+ 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. +

+

PLAINTEXT

+

+ 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: +

+    PLAINTEXT://host.name:port
+            
+

+

SSL

+

+ 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: +

+    SSL://host.name:port
+            
+ In addition, the processor must have an SSL Context Service selected. +

+

+ 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. +

+

+ 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. +

+

SASL_PLAINTEXT

+

+ 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: +

+    SASL_PLAINTEXT://host.name:port
+            
+ In addition, the Kerberos Service Name must be specified in the processor. +

+

SASL_PLAINTEXT - GSSAPI

+

+ 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: +

+    java.arg.16=-Djava.security.auth.login.config=/path/to/kafka_client_jaas.conf
+            
+

+

+ An example of the JAAS config file would be the following: +

+    KafkaClient {
+        com.sun.security.auth.module.Krb5LoginModule required
+        useKeyTab=true
+        storeKey=true
+        keyTab="/path/to/nifi.keytab"
+        serviceName="kafka"
+        principal="nifi@YOURREALM.COM";
+    };
+            
+ NOTE: The serviceName in the JAAS file must match the Kerberos Service Name in the processor. +

+

+ Alternatively, 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. +

+

SASL_PLAINTEXT - PLAIN

+

+ 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: +

+    KafkaClient {
+      org.apache.kafka.common.security.plain.PlainLoginModule required
+      username="nifi"
+      password="nifi-password";
+    };
+            
+

+

+ NOTE: It is not recommended to use a SASL mechanism of PLAIN with SASL_PLAINTEXT, as it would transmit + the username and password unencrypted. +

+

+ NOTE: 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. +

+

SASL_SSL

+

+ 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: +

+    SASL_SSL://host.name:port
+            
+

+

+ See the SASL_PLAINTEXT section for a description of how to provide the proper JAAS configuration + depending on the SASL mechanism (GSSAPI or PLAIN). +

+

+ See the SSL section for a description of how to configure the SSL Context Service based on the + ssl.client.auth property. +

+ + + http://git-wip-us.apache.org/repos/asf/nifi/blob/00b11e82/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-0-11-processors/src/main/resources/docs/org.apache.nifi.processors.kafka.pubsub.ConsumeKafka_0_10/additionalDetails.html ---------------------------------------------------------------------- diff --git a/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-0-11-processors/src/main/resources/docs/org.apache.nifi.processors.kafka.pubsub.ConsumeKafka_0_10/additionalDetails.html b/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-0-11-processors/src/main/resources/docs/org.apache.nifi.processors.kafka.pubsub.ConsumeKafka_0_10/additionalDetails.html deleted file mode 100644 index 760066d..0000000 --- a/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-0-11-processors/src/main/resources/docs/org.apache.nifi.processors.kafka.pubsub.ConsumeKafka_0_10/additionalDetails.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - - ConsumeKafka - - - - -

Description

-

- This Processor polls Apache Kafka - for data using KafkaConsumer API available with Kafka 0.11.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. -

- - -

Security Configuration

-

- 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. -

-

PLAINTEXT

-

- 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: -

-    PLAINTEXT://host.name:port
-            
-

-

SSL

-

- 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: -

-    SSL://host.name:port
-            
- In addition, the processor must have an SSL Context Service selected. -

-

- 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. -

-

- 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. -

-

SASL_PLAINTEXT

-

- 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: -

-    SASL_PLAINTEXT://host.name:port
-            
- In addition, the Kerberos Service Name must be specified in the processor. -

-

SASL_PLAINTEXT - GSSAPI

-

- 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: -

-    java.arg.16=-Djava.security.auth.login.config=/path/to/kafka_client_jaas.conf
-            
-

-

- An example of the JAAS config file would be the following: -

-    KafkaClient {
-        com.sun.security.auth.module.Krb5LoginModule required
-        useKeyTab=true
-        storeKey=true
-        keyTab="/path/to/nifi.keytab"
-        serviceName="kafka"
-        principal="nifi@YOURREALM.COM";
-    };
-            
- NOTE: The serviceName in the JAAS file must match the Kerberos Service Name in the processor. -

-

- Alternatively, 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. -

-

SASL_PLAINTEXT - PLAIN

-

- 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: -

-    KafkaClient {
-      org.apache.kafka.common.security.plain.PlainLoginModule required
-      username="nifi"
-      password="nifi-password";
-    };
-            
-

-

- NOTE: It is not recommended to use a SASL mechanism of PLAIN with SASL_PLAINTEXT, as it would transmit - the username and password unencrypted. -

-

- NOTE: 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. -

-

SASL_SSL

-

- 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: -

-    SASL_SSL://host.name:port
-            
-

-

- See the SASL_PLAINTEXT section for a description of how to provide the proper JAAS configuration - depending on the SASL mechanism (GSSAPI or PLAIN). -

-

- See the SSL section for a description of how to configure the SSL Context Service based on the - ssl.client.auth property. -

- - - http://git-wip-us.apache.org/repos/asf/nifi/blob/00b11e82/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-0-11-processors/src/main/resources/docs/org.apache.nifi.processors.kafka.pubsub.ConsumeKafka_0_11/additionalDetails.html ---------------------------------------------------------------------- diff --git a/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-0-11-processors/src/main/resources/docs/org.apache.nifi.processors.kafka.pubsub.ConsumeKafka_0_11/additionalDetails.html b/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-0-11-processors/src/main/resources/docs/org.apache.nifi.processors.kafka.pubsub.ConsumeKafka_0_11/additionalDetails.html new file mode 100644 index 0000000..760066d --- /dev/null +++ b/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-0-11-processors/src/main/resources/docs/org.apache.nifi.processors.kafka.pubsub.ConsumeKafka_0_11/additionalDetails.html @@ -0,0 +1,143 @@ + + + + + + ConsumeKafka + + + + +

Description

+

+ This Processor polls Apache Kafka + for data using KafkaConsumer API available with Kafka 0.11.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. +

+ + +

Security Configuration

+

+ 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. +

+

PLAINTEXT

+

+ 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: +

+    PLAINTEXT://host.name:port
+            
+

+

SSL

+

+ 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: +

+    SSL://host.name:port
+            
+ In addition, the processor must have an SSL Context Service selected. +

+

+ 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. +

+

+ 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. +

+

SASL_PLAINTEXT

+

+ 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: +

+    SASL_PLAINTEXT://host.name:port
+            
+ In addition, the Kerberos Service Name must be specified in the processor. +

+

SASL_PLAINTEXT - GSSAPI

+

+ 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: +

+    java.arg.16=-Djava.security.auth.login.config=/path/to/kafka_client_jaas.conf
+            
+

+

+ An example of the JAAS config file would be the following: +

+    KafkaClient {
+        com.sun.security.auth.module.Krb5LoginModule required
+        useKeyTab=true
+        storeKey=true
+        keyTab="/path/to/nifi.keytab"
+        serviceName="kafka"
+        principal="nifi@YOURREALM.COM";
+    };
+            
+ NOTE: The serviceName in the JAAS file must match the Kerberos Service Name in the processor. +

+

+ Alternatively, 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. +

+

SASL_PLAINTEXT - PLAIN

+

+ 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: +

+    KafkaClient {
+      org.apache.kafka.common.security.plain.PlainLoginModule required
+      username="nifi"
+      password="nifi-password";
+    };
+            
+

+

+ NOTE: It is not recommended to use a SASL mechanism of PLAIN with SASL_PLAINTEXT, as it would transmit + the username and password unencrypted. +

+

+ NOTE: 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. +

+

SASL_SSL

+

+ 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: +

+    SASL_SSL://host.name:port
+            
+

+

+ See the SASL_PLAINTEXT section for a description of how to provide the proper JAAS configuration + depending on the SASL mechanism (GSSAPI or PLAIN). +

+

+ See the SSL section for a description of how to configure the SSL Context Service based on the + ssl.client.auth property. +

+ + + http://git-wip-us.apache.org/repos/asf/nifi/blob/00b11e82/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-0-11-processors/src/main/resources/docs/org.apache.nifi.processors.kafka.pubsub.PublishKafkaRecord_0_10/additionalDetails.html ---------------------------------------------------------------------- diff --git a/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-0-11-processors/src/main/resources/docs/org.apache.nifi.processors.kafka.pubsub.PublishKafkaRecord_0_10/additionalDetails.html b/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-0-11-processors/src/main/resources/docs/org.apache.nifi.processors.kafka.pubsub.PublishKafkaRecord_0_10/additionalDetails.html deleted file mode 100644 index 9d5882e..0000000 --- a/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-0-11-processors/src/main/resources/docs/org.apache.nifi.processors.kafka.pubsub.PublishKafkaRecord_0_10/additionalDetails.html +++ /dev/null @@ -1,144 +0,0 @@ - - - - - - PublishKafka - - - - -

Description

-

- This Processor puts the contents of a FlowFile to a Topic in - Apache Kafka using KafkaProducer API available - with Kafka 0.11.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 <Kafka Key> Property. -

- - -

Security Configuration

-

- 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. -

-

PLAINTEXT

-

- 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: -

-    PLAINTEXT://host.name:port
-            
-

-

SSL

-

- 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: -

-    SSL://host.name:port
-            
- In addition, the processor must have an SSL Context Service selected. -

-

- 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. -

-

- 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. -

-

SASL_PLAINTEXT

-

- 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: -

-    SASL_PLAINTEXT://host.name:port
-            
- In addition, the Kerberos Service Name must be specified in the processor. -

-

SASL_PLAINTEXT - GSSAPI

-

- 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: -

-    java.arg.16=-Djava.security.auth.login.config=/path/to/kafka_client_jaas.conf
-            
-

-

- An example of the JAAS config file would be the following: -

-    KafkaClient {
-        com.sun.security.auth.module.Krb5LoginModule required
-        useKeyTab=true
-        storeKey=true
-        keyTab="/path/to/nifi.keytab"
-        serviceName="kafka"
-        principal="nifi@YOURREALM.COM";
-    };
-            
- NOTE: The serviceName in the JAAS file must match the Kerberos Service Name in the processor. -

-

- Alternatively, 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. -

-

SASL_PLAINTEXT - PLAIN

-

- 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: -

-    KafkaClient {
-      org.apache.kafka.common.security.plain.PlainLoginModule required
-      username="nifi"
-      password="nifi-password";
-    };
-            
-

-

- NOTE: It is not recommended to use a SASL mechanism of PLAIN with SASL_PLAINTEXT, as it would transmit - the username and password unencrypted. -

-

- NOTE: 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. -

-

SASL_SSL

-

- 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: -

-    SASL_SSL://host.name:port
-            
-

-

- See the SASL_PLAINTEXT section for a description of how to provide the proper JAAS configuration - depending on the SASL mechanism (GSSAPI or PLAIN). -

-

- See the SSL section for a description of how to configure the SSL Context Service based on the - ssl.client.auth property. -

- - http://git-wip-us.apache.org/repos/asf/nifi/blob/00b11e82/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-0-11-processors/src/main/resources/docs/org.apache.nifi.processors.kafka.pubsub.PublishKafkaRecord_0_11/additionalDetails.html ---------------------------------------------------------------------- diff --git a/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-0-11-processors/src/main/resources/docs/org.apache.nifi.processors.kafka.pubsub.PublishKafkaRecord_0_11/additionalDetails.html b/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-0-11-processors/src/main/resources/docs/org.apache.nifi.processors.kafka.pubsub.PublishKafkaRecord_0_11/additionalDetails.html new file mode 100644 index 0000000..9d5882e --- /dev/null +++ b/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-0-11-processors/src/main/resources/docs/org.apache.nifi.processors.kafka.pubsub.PublishKafkaRecord_0_11/additionalDetails.html @@ -0,0 +1,144 @@ + + + + + + PublishKafka + + + + +

Description

+

+ This Processor puts the contents of a FlowFile to a Topic in + Apache Kafka using KafkaProducer API available + with Kafka 0.11.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 <Kafka Key> Property. +

+ + +

Security Configuration

+

+ 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. +

+

PLAINTEXT

+

+ 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: +

+    PLAINTEXT://host.name:port
+            
+

+

SSL

+

+ 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: +

+    SSL://host.name:port
+            
+ In addition, the processor must have an SSL Context Service selected. +

+

+ 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. +

+

+ 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. +

+

SASL_PLAINTEXT

+

+ 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: +

+    SASL_PLAINTEXT://host.name:port
+            
+ In addition, the Kerberos Service Name must be specified in the processor. +

+

SASL_PLAINTEXT - GSSAPI

+

+ 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: +

+    java.arg.16=-Djava.security.auth.login.config=/path/to/kafka_client_jaas.conf
+            
+

+

+ An example of the JAAS config file would be the following: +

+    KafkaClient {
+        com.sun.security.auth.module.Krb5LoginModule required
+        useKeyTab=true
+        storeKey=true
+        keyTab="/path/to/nifi.keytab"
+        serviceName="kafka"
+        principal="nifi@YOURREALM.COM";
+    };
+            
+ NOTE: The serviceName in the JAAS file must match the Kerberos Service Name in the processor. +

+

+ Alternatively, 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. +

+

SASL_PLAINTEXT - PLAIN

+

+ 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: +

+    KafkaClient {
+      org.apache.kafka.common.security.plain.PlainLoginModule required
+      username="nifi"
+      password="nifi-password";
+    };
+            
+

+

+ NOTE: It is not recommended to use a SASL mechanism of PLAIN with SASL_PLAINTEXT, as it would transmit + the username and password unencrypted. +

+

+ NOTE: 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. +

+

SASL_SSL

+

+ 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: +

+    SASL_SSL://host.name:port
+            
+

+

+ See the SASL_PLAINTEXT section for a description of how to provide the proper JAAS configuration + depending on the SASL mechanism (GSSAPI or PLAIN). +

+

+ See the SSL section for a description of how to configure the SSL Context Service based on the + ssl.client.auth property. +

+ + http://git-wip-us.apache.org/repos/asf/nifi/blob/00b11e82/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-0-11-processors/src/main/resources/docs/org.apache.nifi.processors.kafka.pubsub.PublishKafka_0_10/additionalDetails.html ---------------------------------------------------------------------- diff --git a/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-0-11-processors/src/main/resources/docs/org.apache.nifi.processors.kafka.pubsub.PublishKafka_0_10/additionalDetails.html b/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-0-11-processors/src/main/resources/docs/org.apache.nifi.processors.kafka.pubsub.PublishKafka_0_10/additionalDetails.html deleted file mode 100644 index 4d8de4e..0000000 --- a/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-0-11-processors/src/main/resources/docs/org.apache.nifi.processors.kafka.pubsub.PublishKafka_0_10/additionalDetails.html +++ /dev/null @@ -1,156 +0,0 @@ - - - - - - PublishKafka - - - - -

Description

-

- This Processor puts the contents of a FlowFile to a Topic in - Apache Kafka using KafkaProducer API available - with Kafka 0.11.x API. The content of a FlowFile becomes the contents of a Kafka message. - This message is optionally assigned a key by using the <Kafka Key> Property. -

- -

- The Processor allows the user to configure an optional Message Demarcator that - can be used to send many messages per FlowFile. For example, a \n 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. -

- - -

Security Configuration

-

- 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. -

-

PLAINTEXT

-

- 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: -

-    PLAINTEXT://host.name:port
-            
-

-

SSL

-

- 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: -

-    SSL://host.name:port
-            
- In addition, the processor must have an SSL Context Service selected. -

-

- 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. -

-

- 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. -

-

SASL_PLAINTEXT

-

- 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: -

-    SASL_PLAINTEXT://host.name:port
-            
- In addition, the Kerberos Service Name must be specified in the processor. -

-

SASL_PLAINTEXT - GSSAPI

-

- 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: -

-    java.arg.16=-Djava.security.auth.login.config=/path/to/kafka_client_jaas.conf
-            
-

-

- An example of the JAAS config file would be the following: -

-    KafkaClient {
-        com.sun.security.auth.module.Krb5LoginModule required
-        useKeyTab=true
-        storeKey=true
-        keyTab="/path/to/nifi.keytab"
-        serviceName="kafka"
-        principal="nifi@YOURREALM.COM";
-    };
-            
- NOTE: The serviceName in the JAAS file must match the Kerberos Service Name in the processor. -

-

- Alternatively, 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. -

-

SASL_PLAINTEXT - PLAIN

-

- 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: -

-    KafkaClient {
-      org.apache.kafka.common.security.plain.PlainLoginModule required
-      username="nifi"
-      password="nifi-password";
-    };
-            
-

-

- NOTE: It is not recommended to use a SASL mechanism of PLAIN with SASL_PLAINTEXT, as it would transmit - the username and password unencrypted. -

-

- NOTE: 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. -

-

SASL_SSL

-

- 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: -

-    SASL_SSL://host.name:port
-            
-

-

- See the SASL_PLAINTEXT section for a description of how to provide the proper JAAS configuration - depending on the SASL mechanism (GSSAPI or PLAIN). -

-

- See the SSL section for a description of how to configure the SSL Context Service based on the - ssl.client.auth property. -

- - http://git-wip-us.apache.org/repos/asf/nifi/blob/00b11e82/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-0-11-processors/src/main/resources/docs/org.apache.nifi.processors.kafka.pubsub.PublishKafka_0_11/additionalDetails.html ---------------------------------------------------------------------- diff --git a/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-0-11-processors/src/main/resources/docs/org.apache.nifi.processors.kafka.pubsub.PublishKafka_0_11/additionalDetails.html b/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-0-11-processors/src/main/resources/docs/org.apache.nifi.processors.kafka.pubsub.PublishKafka_0_11/additionalDetails.html new file mode 100644 index 0000000..4d8de4e --- /dev/null +++ b/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-0-11-processors/src/main/resources/docs/org.apache.nifi.processors.kafka.pubsub.PublishKafka_0_11/additionalDetails.html @@ -0,0 +1,156 @@ + + + + + + PublishKafka + + + + +

Description

+

+ This Processor puts the contents of a FlowFile to a Topic in + Apache Kafka using KafkaProducer API available + with Kafka 0.11.x API. The content of a FlowFile becomes the contents of a Kafka message. + This message is optionally assigned a key by using the <Kafka Key> Property. +

+ +

+ The Processor allows the user to configure an optional Message Demarcator that + can be used to send many messages per FlowFile. For example, a \n 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. +

+ + +

Security Configuration

+

+ 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. +

+

PLAINTEXT

+

+ 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: +

+    PLAINTEXT://host.name:port
+            
+

+

SSL

+

+ 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: +

+    SSL://host.name:port
+            
+ In addition, the processor must have an SSL Context Service selected. +

+

+ 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. +

+

+ 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. +

+

SASL_PLAINTEXT

+

+ 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: +

+    SASL_PLAINTEXT://host.name:port
+            
+ In addition, the Kerberos Service Name must be specified in the processor. +

+

SASL_PLAINTEXT - GSSAPI

+

+ 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: +

+    java.arg.16=-Djava.security.auth.login.config=/path/to/kafka_client_jaas.conf
+            
+

+

+ An example of the JAAS config file would be the following: +

+    KafkaClient {
+        com.sun.security.auth.module.Krb5LoginModule required
+        useKeyTab=true
+        storeKey=true
+        keyTab="/path/to/nifi.keytab"
+        serviceName="kafka"
+        principal="nifi@YOURREALM.COM";
+    };
+            
+ NOTE: The serviceName in the JAAS file must match the Kerberos Service Name in the processor. +

+

+ Alternatively, 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. +

+

SASL_PLAINTEXT - PLAIN

+

+ 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: +

+    KafkaClient {
+      org.apache.kafka.common.security.plain.PlainLoginModule required
+      username="nifi"
+      password="nifi-password";
+    };
+            
+

+

+ NOTE: It is not recommended to use a SASL mechanism of PLAIN with SASL_PLAINTEXT, as it would transmit + the username and password unencrypted. +

+

+ NOTE: 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. +

+

SASL_SSL

+

+ 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: +

+    SASL_SSL://host.name:port
+            
+

+

+ See the SASL_PLAINTEXT section for a description of how to provide the proper JAAS configuration + depending on the SASL mechanism (GSSAPI or PLAIN). +

+

+ See the SSL section for a description of how to configure the SSL Context Service based on the + ssl.client.auth property. +

+ + http://git-wip-us.apache.org/repos/asf/nifi/blob/00b11e82/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-1-0-nar/pom.xml ---------------------------------------------------------------------- diff --git a/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-1-0-nar/pom.xml b/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-1-0-nar/pom.xml new file mode 100644 index 0000000..f1806a1 --- /dev/null +++ b/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-1-0-nar/pom.xml @@ -0,0 +1,40 @@ + + + 4.0.0 + + org.apache.nifi + nifi-kafka-bundle + 1.5.0-SNAPSHOT + + nifi-kafka-1-0-nar + nar + NiFi NAR for interacting with Apache Kafka 1.0 + + true + true + + + + org.apache.nifi + nifi-kafka-1-0-processors + + + org.apache.nifi + nifi-standard-services-api-nar + nar + + + http://git-wip-us.apache.org/repos/asf/nifi/blob/00b11e82/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-1-0-nar/src/main/resources/META-INF/LICENSE ---------------------------------------------------------------------- diff --git a/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-1-0-nar/src/main/resources/META-INF/LICENSE b/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-1-0-nar/src/main/resources/META-INF/LICENSE new file mode 100644 index 0000000..43a2a3b --- /dev/null +++ b/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-1-0-nar/src/main/resources/META-INF/LICENSE @@ -0,0 +1,233 @@ + + Apache License + Version 2.0, January 2004 + http://www.apache.org/licenses/ + + TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION + + 1. Definitions. + + "License" shall mean the terms and conditions for use, reproduction, + and distribution as defined by Sections 1 through 9 of this document. + + "Licensor" shall mean the copyright owner or entity authorized by + the copyright owner that is granting the License. + + "Legal Entity" shall mean the union of the acting entity and all + other entities that control, are controlled by, or are under common + control with that entity. For the purposes of this definition, + "control" means (i) the power, direct or indirect, to cause the + direction or management of such entity, whether by contract or + otherwise, or (ii) ownership of fifty percent (50%) or more of the + outstanding shares, or (iii) beneficial ownership of such entity. + + "You" (or "Your") shall mean an individual or Legal Entity + exercising permissions granted by this License. + + "Source" form shall mean the preferred form for making modifications, + including but not limited to software source code, documentation + source, and configuration files. + + "Object" form shall mean any form resulting from mechanical + transformation or translation of a Source form, including but + not limited to compiled object code, generated documentation, + and conversions to other media types. + + "Work" shall mean the work of authorship, whether in Source or + Object form, made available under the License, as indicated by a + copyright notice that is included in or attached to the work + (an example is provided in the Appendix below). + + "Derivative Works" shall mean any work, whether in Source or Object + form, that is based on (or derived from) the Work and for which the + editorial revisions, annotations, elaborations, or other modifications + represent, as a whole, an original work of authorship. For the purposes + of this License, Derivative Works shall not include works that remain + separable from, or merely link (or bind by name) to the interfaces of, + the Work and Derivative Works thereof. + + "Contribution" shall mean any work of authorship, including + the original version of the Work and any modifications or additions + to that Work or Derivative Works thereof, that is intentionally + submitted to Licensor for inclusion in the Work by the copyright owner + or by an individual or Legal Entity authorized to submit on behalf of + the copyright owner. For the purposes of this definition, "submitted" + means any form of electronic, verbal, or written communication sent + to the Licensor or its representatives, including but not limited to + communication on electronic mailing lists, source code control systems, + and issue tracking systems that are managed by, or on behalf of, the + Licensor for the purpose of discussing and improving the Work, but + excluding communication that is conspicuously marked or otherwise + designated in writing by the copyright owner as "Not a Contribution." + + "Contributor" shall mean Licensor and any individual or Legal Entity + on behalf of whom a Contribution has been received by Licensor and + subsequently incorporated within the Work. + + 2. Grant of Copyright License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + copyright license to reproduce, prepare Derivative Works of, + publicly display, publicly perform, sublicense, and distribute the + Work and such Derivative Works in Source or Object form. + + 3. Grant of Patent License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + (except as stated in this section) patent license to make, have made, + use, offer to sell, sell, import, and otherwise transfer the Work, + where such license applies only to those patent claims licensable + by such Contributor that are necessarily infringed by their + Contribution(s) alone or by combination of their Contribution(s) + with the Work to which such Contribution(s) was submitted. If You + institute patent litigation against any entity (including a + cross-claim or counterclaim in a lawsuit) alleging that the Work + or a Contribution incorporated within the Work constitutes direct + or contributory patent infringement, then any patent licenses + granted to You under this License for that Work shall terminate + as of the date such litigation is filed. + + 4. Redistribution. You may reproduce and distribute copies of the + Work or Derivative Works thereof in any medium, with or without + modifications, and in Source or Object form, provided that You + meet the following conditions: + + (a) You must give any other recipients of the Work or + Derivative Works a copy of this License; and + + (b) You must cause any modified files to carry prominent notices + stating that You changed the files; and + + (c) You must retain, in the Source form of any Derivative Works + that You distribute, all copyright, patent, trademark, and + attribution notices from the Source form of the Work, + excluding those notices that do not pertain to any part of + the Derivative Works; and + + (d) If the Work includes a "NOTICE" text file as part of its + distribution, then any Derivative Works that You distribute must + include a readable copy of the attribution notices contained + within such NOTICE file, excluding those notices that do not + pertain to any part of the Derivative Works, in at least one + of the following places: within a NOTICE text file distributed + as part of the Derivative Works; within the Source form or + documentation, if provided along with the Derivative Works; or, + within a display generated by the Derivative Works, if and + wherever such third-party notices normally appear. The contents + of the NOTICE file are for informational purposes only and + do not modify the License. You may add Your own attribution + notices within Derivative Works that You distribute, alongside + or as an addendum to the NOTICE text from the Work, provided + that such additional attribution notices cannot be construed + as modifying the License. + + You may add Your own copyright statement to Your modifications and + may provide additional or different license terms and conditions + for use, reproduction, or distribution of Your modifications, or + for any such Derivative Works as a whole, provided Your use, + reproduction, and distribution of the Work otherwise complies with + the conditions stated in this License. + + 5. Submission of Contributions. Unless You explicitly state otherwise, + any Contribution intentionally submitted for inclusion in the Work + by You to the Licensor shall be under the terms and conditions of + this License, without any additional terms or conditions. + Notwithstanding the above, nothing herein shall supersede or modify + the terms of any separate license agreement you may have executed + with Licensor regarding such Contributions. + + 6. Trademarks. This License does not grant permission to use the trade + names, trademarks, service marks, or product names of the Licensor, + except as required for reasonable and customary use in describing the + origin of the Work and reproducing the content of the NOTICE file. + + 7. Disclaimer of Warranty. Unless required by applicable law or + agreed to in writing, Licensor provides the Work (and each + Contributor provides its Contributions) on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or + implied, including, without limitation, any warranties or conditions + of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A + PARTICULAR PURPOSE. You are solely responsible for determining the + appropriateness of using or redistributing the Work and assume any + risks associated with Your exercise of permissions under this License. + + 8. Limitation of Liability. In no event and under no legal theory, + whether in tort (including negligence), contract, or otherwise, + unless required by applicable law (such as deliberate and grossly + negligent acts) or agreed to in writing, shall any Contributor be + liable to You for damages, including any direct, indirect, special, + incidental, or consequential damages of any character arising as a + result of this License or out of the use or inability to use the + Work (including but not limited to damages for loss of goodwill, + work stoppage, computer failure or malfunction, or any and all + other commercial damages or losses), even if such Contributor + has been advised of the possibility of such damages. + + 9. Accepting Warranty or Additional Liability. While redistributing + the Work or Derivative Works thereof, You may choose to offer, + and charge a fee for, acceptance of support, warranty, indemnity, + or other liability obligations and/or rights consistent with this + License. However, in accepting such obligations, You may act only + on Your own behalf and on Your sole responsibility, not on behalf + of any other Contributor, and only if You agree to indemnify, + defend, and hold each Contributor harmless for any liability + incurred by, or claims asserted against, such Contributor by reason + of your accepting any such warranty or additional liability. + + END OF TERMS AND CONDITIONS + + APPENDIX: How to apply the Apache License to your work. + + To apply the Apache License to your work, attach the following + boilerplate notice, with the fields enclosed by brackets "[]" + replaced with your own identifying information. (Don't include + the brackets!) The text should be enclosed in the appropriate + comment syntax for the file format. We also recommend that a + file or class name and description of purpose be included on the + same "printed page" as the copyright notice for easier + identification within third-party archives. + + Copyright [yyyy] [name of copyright owner] + + Licensed 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. + +APACHE NIFI SUBCOMPONENTS: + +The Apache NiFi project contains subcomponents with separate copyright +notices and license terms. Your use of the source code for the these +subcomponents is subject to the terms and conditions of the following +licenses. + + The binary distribution of this product bundles 'Bouncy Castle JDK 1.5' + under an MIT style license. + + Copyright (c) 2000 - 2015 The Legion of the Bouncy Castle Inc. (http://www.bouncycastle.org) + + Permission is hereby granted, free of charge, to any person obtaining a copy + of this software and associated documentation files (the "Software"), to deal + in the Software without restriction, including without limitation the rights + to use, copy, modify, merge, publish, distribute, sublicense, and/or sell + copies of the Software, and to permit persons to whom the Software is + furnished to do so, subject to the following conditions: + + The above copyright notice and this permission notice shall be included in + all copies or substantial portions of the Software. + + THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR + IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, + FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE + AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER + LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, + OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN + THE SOFTWARE. + http://git-wip-us.apache.org/repos/asf/nifi/blob/00b11e82/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-1-0-nar/src/main/resources/META-INF/NOTICE ---------------------------------------------------------------------- diff --git a/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-1-0-nar/src/main/resources/META-INF/NOTICE b/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-1-0-nar/src/main/resources/META-INF/NOTICE new file mode 100644 index 0000000..03af5fd --- /dev/null +++ b/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-1-0-nar/src/main/resources/META-INF/NOTICE @@ -0,0 +1,83 @@ +nifi-kafka-nar +Copyright 2014-2017 The Apache Software Foundation + +This product includes software developed at +The Apache Software Foundation (http://www.apache.org/). + +****************** +Apache Software License v2 +****************** + +The following binary components are provided under the Apache Software License v2 + + (ASLv2) Apache Commons Lang + The following NOTICE information applies: + Apache Commons Lang + Copyright 2001-2017 The Apache Software Foundation + + This product includes software from the Spring Framework, + under the Apache License 2.0 (see: StringUtils.containsWhitespace()) + + (ASLv2) Apache Commons IO + The following NOTICE information applies: + Apache Commons IO + Copyright 2002-2016 The Apache Software Foundation + + (ASLv2) Apache Commons Codec + The following NOTICE information applies: + Apache Commons Codec + Copyright 2002-2014 The Apache Software Foundation + + src/test/org/apache/commons/codec/language/DoubleMetaphoneTest.java + contains test data from http://aspell.net/test/orig/batch0.tab. + Copyright (C) 2002 Kevin Atkinson (kevina@gnu.org) + + =============================================================================== + + The content of package org.apache.commons.codec.language.bm has been translated + from the original php source code available at http://stevemorse.org/phoneticinfo.htm + with permission from the original authors. + Original source copyright: + Copyright (c) 2008 Alexander Beider & Stephen P. Morse. + + (ASLv2) Apache Kafka + The following NOTICE information applies: + Apache Kafka + Copyright 2012 The Apache Software Foundation. + + (ASLv2) Snappy Java + The following NOTICE information applies: + This product includes software developed by Google + Snappy: http://code.google.com/p/snappy/ (New BSD License) + + This product includes software developed by Apache + PureJavaCrc32C from apache-hadoop-common http://hadoop.apache.org/ + (Apache 2.0 license) + + This library containd statically linked libstdc++. This inclusion is allowed by + "GCC RUntime Library Exception" + http://gcc.gnu.org/onlinedocs/libstdc++/manual/license.html + + (ASLv2) Jackson JSON processor + The following NOTICE information applies: + # Jackson JSON processor + + Jackson is a high-performance, Free/Open Source JSON processing library. + It was originally written by Tatu Saloranta (tatu.saloranta@iki.fi), and has + been in development since 2007. + It is currently developed by a community of developers, as well as supported + commercially by FasterXML.com. + + ## Licensing + + Jackson core and extension components may licensed under different licenses. + To find the details that apply to this artifact see the accompanying LICENSE file. + For more information, including possible other licensing options, contact + FasterXML.com (http://fasterxml.com). + + ## Credits + + A list of contributors may be found from CREDITS file, which is included + in some artifacts (usually source distributions); but is always available + from the source code management (SCM) system project uses. +