![]() The complementary NiFi processor for sending messages is PublishKafka_2_6. ConsumeKafka_2_6Ĭonsumes messages from Apache Kafka specifically built against the Kafka 2.6 Consumer API. The complementary NiFi processor for sending messages is PublishKafka_2_0. ConsumeKafka_2_0Ĭonsumes messages from Apache Kafka specifically built against the Kafka 2.0 Consumer API. The complementary NiFi processor for sending messages is PublishKafka_1_0. ConsumeKafka_1_0Ĭonsumes messages from Apache Kafka specifically built against the Kafka 1.0 Consumer API. The complementary NiFi processor for sending messages is PublishKafka_0_11. ![]() ConsumeKafka_0_11Ĭonsumes messages from Apache Kafka specifically built against the Kafka 0.11.x Consumer API. The other types will have their raw contents as byte array transferred into the flowfile. MapMessages will be transformed into JSONs and then into byte arrays. JMS attributes such as headers and properties will be copied as FlowFile attributes. The raw-bytes of each received email message are written as contents of the FlowFile ConsumeJMSĬonsumes JMS Message of type BytesMessage, TextMessage, ObjectMessage, MapMessage or StreamMessage transforming its content to a FlowFile and transitioning it to ‘success’ relationship. ConsumeIMAPĬonsumes messages from Email Server using IMAP protocol. If the ‘Batch Size’ is set, the configured number of messages will be pulled in a single request, else only one message will be pulled. The raw-bytes of each received email message are written as contents of the FlowFile ConsumeGCPubSubĬonsumes message from the configured Google Cloud PubSub subscription. ConsumeEWSĬonsumes messages from Microsoft Exchange using Exchange Web Services. Receives messages from Azure Event Hubs, writing the contents of the message to the content of the FlowFile. Each message that is received from the AMQP Broker will be emitted as its own FlowFile to the ‘success’ relationship. ConsumeAMQPĬonsumes AMQP Messages from an AMQP Broker using the AMQP 0.9.1 protocol. ![]() FlowFiles are transferred to downstream relationships according to received message types as WebSocket client configured with this processor receives messages from remote WebSocket server. This processor operates in a very memory efficient way so very large objects well beyond the heap size are generally fine to process ConnectWebSocketĪcts as a WebSocket client endpoint to interact with a remote WebSocket server. CompressContentĬompresses or decompresses the contents of FlowFiles using a user-specified compression algorithm and updates the mime.type attribute as appropriate. CompareFuzzyHashĬompares an attribute containing a Fuzzy Hash against a file containing a list of fuzzy hashes, appending an attribute to the FlowFile in case of a successful match. Events are output as individual flow files ordered by the time at which the operation occurred. CDC Events include INSERT, UPDATE, DELETE operations. Retrieves Change Data Capture (CDC) events from a MySQL database. Base64EncodeContentĮncodes or decodes content to and from base64 CalculateRecordStatsĪ processor that can count the number of items in a record set, as well as provide counts based on user-defined criteria on subsets of the record set. The resulting JSON can be written to either a new Attribute ‘JSONAttributes’ or written to the FlowFile as content. Generates a JSON representation of the input FlowFile Attributes. Any double quote characters in the attribute value are escaped with another double quote. If the attribute value contains a comma, newline or double quote, then the attribute value will be escaped with double quotes. The resulting CSV can be written to either a newly generated attribute named ‘CSVAttributes’ or written to the FlowFile as content. Generates a CSV representation of the input FlowFile Attributes. Each FlowFile will be emitted with the count of FlowFiles and total aggregate value of values processed in the current time window. Track a Rolling Window based on evaluating an Expression Language expression on each FlowFile and add that value to the processor’s state. ![]() In 1.12.1, there are 11 new processors from the previous version, 1.11.3. For other nifi versions, please reference our default processors post.Ĭheck the Apache nifi site for downloads or any nifi version or for current version docs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |