Applying a NiFi flow patch to NiFi Registry

Complete the following steps to apply patch to NiFi Registry.

Procedure

Open a web browser and log in to the HCL License and Delivery portal website to download flow patch JSON.
Place the flow patch JSON file into the /patches directory. If this folder is mapped to an external storage volume, you can place the patch JSON there without logging into the Registry container. To ensure that your patch JSON file is loaded correctly, run the touch command against the file. This ensures that the modification timestamp on this file is current.
The JSON flow patch is applied to existing or new NiFi registry flows automatically. Check for the message Flow Import from or patches concluded at <timestamp> in the registry container logs. This notification shows that the patch has been applied successfully.
In previous versions, following the update of your NiFi registry you had to also update the ingest API. It was necessary to run the upgrade API to synchronize with the update registry and manually rebuild your connectors before any changes would be live. Now, rather than rebuilding your connectors, you can select the particular pipe you want to update and change the version by using the upgradeVersion API. The upgrade API updates the connector and rebuilds it, whereas the upgradeVersion API upgrades the version of a particular pipe across the Nifi workspace. Once the patch is applied and a new version of the flow is ready, it will appear in the NiFi Registry when you import from NiFi. You can either change the version of the pipe manually from the Nifi UI or use a new ingest endpoint upgradeVersion that updates the version number of that pipe across the Nifi workspace.
You can use an alternative approach if you do not want to use the Ingest API to do the update. In this case, perform the following steps:
1. Open your NiFi workspace interface at https://nifi-host:nifi-port/nifi/ and ensure that you do not have any stale or locally modified connectors on the canvas. If you do have stale connectors, make a backup of local changes.
2. Restart the ingest container.
3. Look for this message in the Docker container logs to determine whether the pipe upgrade has been completed:
```
Reset and Upgrade of all the pipes successfully completed.
```
4. Manually upgrade any connector connectorName for which you get this message:
```
Upgrade failed for pipe: connectorName. It needs to be upgraded manually.
```
  Note: If you use this approach, set the environment variable AUTO_UPDATE_PIPE_VERSION to true. The default value for this variable is false.