...
To optimize the NiFi directory structure for upgrade:
Move the following directories out of the NiFi installation directory:
Database repository
All content repositories
Flowfile repository
NiFi log repository
All provenance repositories
See the System Administrator's Guide for information on options for creating these repositories to optimize performance and stability.
Move static items that do not change from version to version out of the conf directory. These items include:
flow.xml.gz
authorized-users.xml
The templates directory
...
Anchor | ||||
---|---|---|---|---|
|
...
If you have written any custom NARs, first test and validate them in a separate new NiFi release sandbox prior to upgrading. The verified NARs can be preserved during the upgrade by storing them in a centralized location as follows:
Create a second library directory, called
custom_lib
.Move your custom NARs to this new lib directory.
Add a new line to the
nifi.properties
file to specify this new lib directory:
nifi.nar.library.directory=./lib
nifi.nar.library.directory.custom=/opt/configuration_resources/custom_lib
Anchor | ||||
---|---|---|---|---|
|
If you have modified any of the default NAR files, an upgrade will overwrite these changes. To preserve the customization:
Identify and save the changes you have made to the default NAR files in your existing instance.
Perform your upgrade toNiFi 1.0.0.
Redo the changes you have made to the NAR files in your NiFi 1.0.0 instance.