Moving files between NiFi and S3, Azure Blob or Data Lake Storage and Google Cloud Storage: list, fetch and put patterns, credentials through controller services, and cross-cloud transfer flows.
Pulling incremental data from relational databases with QueryDatabaseTableRecord and writing records with PutDatabaseRecord: connection pools, maximum-value columns, primary node scheduling and the UPDATE key caveat.
Streaming MySQL inserts, updates and deletes into NiFi flows with CaptureChangeMySQL: binlog prerequisites, event ordering, grouping by transaction and handling restarts. Narrower than polling-based JDBC ingestion.
Indexing and querying Elasticsearch from NiFi with PutElasticsearchRecord, JSON query and consume processors: bulk batching, per-document operations through record paths and supported Elasticsearch versions.
Extracting Salesforce sObject records incrementally with QuerySalesforceObject and writing back with PutSalesforceObject: age-field incremental loads, soft-deleted records, primary node scheduling and custom SOQL limits.
Writing records into Iceberg tables from NiFi with PutIcebergRecord, a REST catalog service and S3, GCS or ADLS file IO providers, for teams feeding a lakehouse from operational sources.
Routing logs and events from NiFi into Splunk through HEC with PutSplunkHTTP and indexing acknowledgement, or pulling search results with GetSplunk, including using NiFi to filter and reduce data before it reaches Splunk.
Consuming and publishing Kafka topics from NiFi 2 with ConsumeKafka, PublishKafka and the Kafka3ConnectionService: record readers and writers, output strategies for keys and headers, parse failures, Amazon MSK connections and moving off the old versioned Kafka processors.
Loading records into BigQuery tables from NiFi with PutBigQuery: the record reader that drives the schema, streaming versus batch writes through the Storage Write API, exactly-once delivery with stream offsets, and fields that silently drop when they do not match the table.
Reading Kinesis Data Streams with ConsumeKinesis and writing with PutKinesisStream or PutKinesisFirehose: DynamoDB checkpointing, IAM permissions, ordering limits across shard splits and merges, and when NiFi is the right consumer for Kinesis data.
Consuming Azure Event Hubs from a NiFi cluster with ConsumeAzureEventHub and checkpoint storage, sending with PutAzureEventHub, how cluster nodes share partitions as a consumer group, and authentication choices.
Pulling Pub/Sub subscriptions into NiFi with ConsumeGCPubSub and publishing with PublishGCPubSub: batch size, the FlowFile, demarcator and record processing strategies, message attributes and throughput trade-offs.
Reading and writing MongoDB collections from NiFi with GetMongoRecord and PutMongoRecord: record readers and writers, insert versus upsert, batch sizing to protect the database, the lack of delete support and the shared MongoDB controller service.
Consuming and publishing JMS queues and topics with ConsumeJMS and PublishJMS: the JMSConnectionFactoryProvider, supplying client libraries from a local directory, message type handling and replacing the removed GetJMSQueue and PutJMS processors.
Moving messages between NiFi and RabbitMQ with ConsumeAMQP and PublishAMQP over AMQP 0.9.1: one FlowFile per message, exchanges and routing keys, unroutable messages when bindings are missing, and acknowledgement behavior.
Subscribing to MQTT brokers with ConsumeMQTT and publishing with PublishMQTT: the internal queue that fills when the run schedule lags, quality of service choices, broker clustering and how NiFi fits between device brokers and analytics stores.
Replacing scripted SFTP jobs with NiFi: the ListSFTP and FetchSFTP pattern for clustered pickup, PutSFTP for delivery, state that prevents duplicate pickups, key-based authentication and managed file transfer patterns with partners.
Picking up and delivering files on Windows Server and Samba shares with ListSmb, FetchSmb and PutSmbFile instead of CIFS mounts: primary node listing, share access control, credentials and folder structures.
Integrating NiFi with REST APIs through InvokeHTTP: methods, attributes sent as headers, OAuth 2.0 access token providers, proxy configuration services, pagination patterns and retry handling for rate-limited APIs.
Accepting pushed data over HTTP with ListenHTTP or building request and response web services with HandleHttpRequest and HandleHttpResponse: supported methods, health checks, TLS, rate limiting after 2.4 and putting a gateway in front.