THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
The following guidance is specific to the indicated version changes. It will contain specific items that users should be aware of when moving between versions:
- Migrating from 1.2.0 to 1.3.0
- No known migration issuesA new property was added to nifi.properties to indicate the maximum number of threads that should be available for cluster request replication. The new property is nifi.cluster.node.protocol.max.threads and defaults to 50. The existing property which set the fixed size of the thread pool nifi.cluster.node.protocol.threads now serves as the initial size and still defaults to 10. However, the new thread pool will add and remove threads as necessary.
- Migrating from 1.1.x to 1.2.0
- With the introduction of component versioning, custom NARs will show up as "unversioned" until they are rebuilt with the latest NAR Maven Plugin (1.2.0). When deploying a rebuilt custom NAR, make sure to remove all previous versions of the NAR from the lib directory.
- The nifi-documentation JAR is no longer directly in the lib directory and is now part of the framework NAR. Make sure there is no left-over version of an old nifi-documentation JAR in the lib directory after upgrading.
- Jetty has been upgraded to version 9.4.2. As a result, TLSv1/1.1 is no longer supported. Users or clients connecting to NiFi through the UI or API now protected with TLS v1.2. Any custom code that consumes the NiFi API needs to use TLS v1.2 or later.
- Migrating from 1.1.x to 1.1.2
- No known migration issues.
- No known migration issues.
...