anchor.diff:  
   === Zero-Leader Clustering
   NiFi employs a Zero-Leader Clustering paradigm. Each node in the cluster has an identical flow definition and performs the same tasks on
  -the data, but each operates on a different set of data. The cluster automatically distributes the data throughout all the active nodes. 
  +the data, but each operates on a different set of data. The cluster automatically distributes the data throughout all the active nodes.
   
   One of the nodes is automatically elected (via Apache
   ZooKeeper) as the Cluster Coordinator. All nodes in the cluster will then send heartbeat/status information
  
positive.code: 	Providing three total locations, including `nifi.provenance.repository.directory.default`.
  |`nifi.provenance.repository.max.storage.time`|The maximum amount of time to keep data provenance information. The default value is `24 hours`.
  |`nifi.provenance.repository.max.storage.size`|The maximum amount of data provenance information to store at a time.
  	The default value is `1 GB`. The Data Provenance capability can consume a great deal of storage space because so much data is kept.
  	For production environments, values of 1-2 TB or more is not uncommon. The repository will write to a single "event file" (or set of
  	"event files" if multiple storage locations are defined, as described above) for some period of time (defined by the
  	`nifi.provenance.repository.rollover.time` and `nifi.provenance.repository.rollover.size` properties). Data is always aged off one file at a time,
  	so it is not advisable to write to a single "event file" for a tremendous amount of time, as it will prevent old data from aging off as smoothly.
  |`nifi.provenance.repository.rollover.time`|The amount of time to wait before rolling over the "event file" that the repository is writing to.
  |`nifi.provenance.repository.rollover.size`|The amount of data to write to a single "event file." The default value is `100 MB`. For production
  	environments where a very large amount of Data Provenance is generated, a value of `1 GB` is also very reasonable.
  |`nifi.provenance.repository.query.threads`|The number of threads to use for Provenance Repository queries. The default value is `2`.
  
negative.code: 
  |====
  |*Property*|*Description*
   |`nifi.provenance.repository.encryption.key.provider.implementation`|This is the fully-qualified class name of the **key provider**. A key provider is the datastore interface for accessing the encryption key to protect the provenance events. There are currently two implementations -- `StaticKeyProvider` which reads a key directly from _nifi.properties_, and `FileBasedKeyProvider` which reads *n* many keys from an encrypted file. The interface is extensible, and HSM-backed or other providers are expected in the future.
   |`nifi.provenance.repository.encryption.key.provider.location`|The path to the key definition resource (empty for `StaticKeyProvider`, `./keys.nkp` or similar path for `FileBasedKeyProvider`). For future providers like an HSM, this may be a connection string or URL.
   |`nifi.provenance.repository.encryption.key.id`|The active key ID to use for encryption (e.g. `Key1`).
  