This article will walk through some of the configuration options within MiNiFi CPP.  As discussed in the Readme, MiNiFi C++ is configured through two files, a config YAML file that includes the flow configuration and general properties for the MiNiFi process. . Users can use the MiNiFi toolkit converter to help create flow configurations from a template exported from a NiFi instance. This document will assume that the YAML configuration will be generated by the toolkit. The Flow Configuration Options section, below, provides some information on each section within the flow configuration file. Note that the examples below are taken from the Github Readme file. System properties is a child page that defines all system properties that are specified in minifi.properties. 

System Properties

  System properties table defines system properties and provides the default value, if one exists for each. 

Flow Configuration options

...

Processors

Processors are defined within the YAML configuration, below. You must specify the number of concurrent tasks, the scheduling strategy, the NiFi class  and properties, if there are any to define.The id is a unique identifier

...

Connections: - name: TransferFilesToRPG id: 471deef6-2a6e-4a7d-912a-81cc17e3a207 source name: GetFile source id: 471deef6-2a6e-4a7d-912a-81cc17e3a206 source relationship name: success destination id: 471deef6-2a6e-4a7d-912a-81cc17e3a204 max work queue size: 0 max work queue data size: 1 MB flowfile expiration: 60 sec

Remote processing Groups

Remote Processing Groups: - name: NiFi Flow id: 471deef6-2a6e-4a7d-912a-81cc17e3a208 url: http://localhost:8080/nifi timeout: 30 secs yield period: 10 sec Input Ports: - id: 471deef6-2a6e-4a7d-912a-81cc17e3a204 name: From Node A max concurrent tasks: 1 Properties: Port: 10001 Host Name: localhost

Provenance Reporting

To add Provenance Reporting to config.yml, define a configuration block like the one below. Define your RPG host, port, and UUID using

...