@plapla Apache NiFi does not have any automated upgrade capability. It is a fully manual process. A typical installation involves downloading the NiFi <version> tar.gz and unpacking it. Unplacking it creates a directory based in that NiFi's version. An upgrade would involve downloading the newer version of NiFi and reading the release notes covering all version between your current version and version you are upgrading to. You'll be looking for anything that may be impactful to your dataflow or installation. I don;t see anything of concern between 1.23.0 and 1.23.2. There are also some old documentation related to upgrades here: https://cwiki.apache.org/confluence/display/NIFI/1.x.0+to+1.x.0+Upgrade But still relevant. Bottom line is you are going to configure the same configuration files found in the NiFi conf file of the new version using the same config files from old version. Make sure that your new NiFi version nifi.properties file configuration related to state, content_repository, provenance_repository, and FlowFile_repository are all pointing to the same directories as the old NiFi version is using. Default configs point at subdirectories within that versions deployment, so be careful. Make sure to use same sensitive props key as well. Somethimes new version introduce new properties in the config files. If no new properties were added you can continue to use original config file. You'll also need to copy over your flow.json.gz which holds everything you added/built via the NiFi UI, users.xml and authorizations.xml files (holds all yoru users and groups and their associated authorizations. Then you can stop the old NiFi and start new. In your case you are simply upgrading to a new patch version of 1.23.0 to 1.23.2, so it is very unlikely that any configurations changed. For you, you could just download the new version 1.23.2, unpack it. On old version: Stop NiFi rename lib directory to lib_1.23.0 copy lib directory from NiFi 1.23.2 you just unpacked in to your 1.23.0 installation. Make sure all file ownership and permissions are correct. Delete NiFi "work" directory. start you NiFi On startup NiFi will recreate the work directory and unpack the new nar versions there. NiFi will then load your flow.json.gz. For each component class it finds in the flow.json.gz, it will upgrade the component to the newer version (only works if only one version for a given component exists, so do not copy new lib inside of old lib directory.). If you found any of the suggestions/solutions provided helped you with your issue, please take a moment to login and click "Accept as Solution" on one or more of them that helped. Thank you, Matt
... View more
