NiFi for XML / RSS / REST Feed Ingest I want to retrieve the status from various Cloud providers and services, including Cloudera, AWS, Azure, and Google. I have found many of the available status APIs will return XML/RSS. We love that format for Apache NiFi, so let's do that. Note: If you are doing development in a non-production environment, try the new NiFi 1.13.1. If you need to run your flows in production on-premise, private cloud, or in the public cloud, then use Cloudera Flow Management. I have separated the processing module "Status" from the input, so I can pass in the input anyway I want. When I move this to a K8 environment, this will become a parameter that I pass in. Stay tuned to Cloudera releases. The flow is pretty simple to process RSS status data. We call the status URL and in the next step easily convert RSS into JSON for easier processing. I split these records and grab just the fields I like. I can easily add additional fields from my metadata for unique id, timestamp, company name, and service name. PutKudu will store my JSON records as Kudu fields at high speed. If something goes wrong, we will try again. Sometimes, the internet is down! But, without this app, how will we know??? We can run a QueryRecord processor to query live fields from the status messages and I will send Spark-related ones to my Slack channel. I can add as many ANSI SQL92 Calcite queries as I wish. It's easy. We were easily able to insert all the status messages to our 'cloudstatus' table. Now, we can query it and use it in reports, dashboards, and visual applications. I don't want to have to go to external sites to get the status alerts, so I will post key ones to a Slack channel. I want to store my status reads in a table for fast analytics and permanent storage. So, I will store it in a Kudu table with Impala on top for fast queries. CREATE TABLE cloudstatus (   `uuid` STRING,   `ts` TIMESTAMP,   `companyname` STRING,   `servicename` STRING,   `title` STRING,   `description` STRING,   `pubdate` STRING,   `link` STRING,   `guid` STRING,   PRIMARY KEY (`uuid`,`ts` ) )   PARTITION BY HASH PARTITIONS 4   STORED AS KUDU TBLPROPERTIES ('kudu.num_tablet_replicas' = '1'); My source code is available here. In the next step, I can write some real-time dashboard with Cloudera Visual Apps, add fast queries on Kafka with Flink SQL, or write some machine learning in Cloudera Machine Learning to finish the application. Join my next live video broadcast to suggest what we do with this data next. Thanks for reading! ... View more

New Features of Apache NiFi 1.13.0 Check it out:   https://twitter.com/pvillard31/status/1361569608327716867?s=27 Download today: Apache NiFi Downloads Release Notes: Release Notes (Apache NiFi) Migration:  Migration Guidance New Features ListenFTP UpdateHiveTable - Hive DDL changes - Hive Update Schema i.e. Data Drift i.e. Hive Schema Migration!!!! SampleRecord - different sampling approaches to records (Interval Sampling, Probabilistic Sampling, Reservoir Sampling) CDC updates Kudu updates AMQP and MQTT integration upgrades ConsumeMQTT - readers, and writers added HTTP access to NiFi by default is now configured to accept connections to 127.0.0.1/localhost only. If you want to allow broader access for some reason for HTTP, and you understand the security implications, you can still control that as always by changing the 'nifi.web.http.host' property in nifi.properties as always. That said, take the time to configure proper HTTPS. We offer detailed instructions and tooling to assist. ConsumeMQTT - add record reader/writer The ability to run NiFi with no GUI as MiNiFi/NiFi combined code base continues. Support for Kudu dates Updated GRPC versions Apache Calcite update PutDatabaseRecord update Here is an example for NiFi ETL Flow: Example NiFi 1.13.0 Flow: ConsumeMQTT:   now with readers UpdateAttribute:   set record.sink.name to kafka and recordreader.name to json. SampleRecord:   sample a few of the records PutRecord:   Use reader and destination service UpdateHiveTable:   new sink Consume from MQTT and read and write to/from records. Some example attributes from a running flow: Connection pools for DatabaseRecordSinks can be JDBC, Hadoop, and Hive. FreeFormTextRecordSetWriter is great for writing any format. RecordSinkService, we will pick Kafka as our destination. KafkaRecordSink from PutRecord The reader will pick JSON in our example based on our UpdateAttribute; we can dynamically change this as data streams. ReaderLookup  - lets you pick a reader based on an attribute. We have defined readers for Parquet, JSON, AVRO, XML, and CSV; no matter the type, I can automagically read it. Great for reusing code and great for cases like our new ListenFTP where you may get sent tons of different files to process. Use one FLOW! RecordSinkService can help you make all our flows generic so you can drop in different sinks/destinations for your writers based on what the data coming in is. This is revolutionary for code reuse. We can write our output in a custom format that could look like a document, HTML, fixed-width, a form letter, weird delimiter, or whatever you need. Sample records using different methods. We use the RecordSinkServiceLookup to allow us to change our sink location dynamically; we are passing in an attribute to choose Kafka. We have pushed our data to Kafka using KafkaRecordSink. We can see our data easily in Streams Messaging Manager (SMM). With a RecordReaderFactory, you can pick readers like the new WindowsEventLogReader. As another output, we can UpdateHiveTable from our data and change the table as needed. Straight From Release Notes: New Feature [NIFI-7386] - AzureStorageCredentialsControllerService should also connect to storage emulator [NIFI-7429] - Add Status History capabilities for system-level metrics [NIFI-7549] - Adding Hazelcast based implementation for DistributedMapCacheClient [NIFI-7624] - Build a ListenFTP processor [NIFI-7745] - Add a SampleRecord processor [NIFI-7796] - Add Prometheus metrics for total bytes received and bytes sent for components [NIFI-7801] - Add acknowledgment check to Splunk [NIFI-7821] - Create a Cassandra implementation of DistributedMapCacheClient [NIFI-7879] - Create record path function for UUID v5 [NIFI-7906] - Add graph processor with the flexibility to query graph database conditioned on flowfile content and attributes [NIFI-7989] - Add Hive "data drift" processor [NIFI-8136] - Allow State Management to be tied to Process Session [NIFI-8142] - Add "on conflict do nothing" feature to PutDatabaseRecord [NIFI-8146] - Allow RecordPath to be used for specifying operation type and data fields when using PutDatabaseRecord [NIFI-8175] - Add a WindowsEventLogReader An update on Cloudera Flow Management! Cloudera Flow Management on DataHub Public Cloud  This minor update has some Schema Registry and Atlas integration updates.   What's New in Cloudera DataFlow for Data Hub 7.2.7 Supported NiFi Processors If that wasn't enough, a new version of MiNiFi C++ Agent! Cloudera Edge Manager 1.2.2 Release February 15, 2021 CEM MiNiFi C++ Agent - 1.21.01 release includes: Support for JSON output in the Consume Windows Even Log processor Full Expression Language support on Windows Full S3 support (List, Fetch, Get, Put) MiNiFi C++ download locations MiNiFi C++ agent updates Remember when you are done. ... View more