...
- When moving between patch (also known as incremental) version changes such as 0.1.0 to 0.1.1 users should be safe to assume a clean upgrade can occur with no risk of behavior changes other than bug fixes and no compatibility issues.
- When moving between minor changes such as 0.1.0 to 0.2.0 users can expect new behaviors and bug fixes but backward compatibility should be protected.
- When moving between major changes such as 0.x.y to 1.0.0 t here may be backward compatibility impacting changes largely focused on removal of deprecated items.
Migrating to 1.21.0
- Refactored OpenID Connect integration changed the Post Logout Redirect URI to avoid using relative paths
- Previous Post Logout Redirect URI Path: /nifi-api/../nifi/logout-complete
- New Post Logout Redirect URI Path: /nifi/logout-complete
- OpenID Connect Identity Providers that support RP-Initiated Logout 1.0 may need to be updated with the new Post Logout Redirect URI
Migrating to 1.19.0
- This release deprecated support for Java 8. Java 11.0.16 is the minimum recommended version
- For users of the apace/nifi* Docker images, note that the base image changed to eclipse-temurin:jre-11 from openjdk:8-jre. This could cause build issues if you were using the Apache NiFi docker image(s) as a base for custom images, or otherwise have functionality that requires packages from the base image and not NiFi itself. It is recommended to test in a dev environment prior to migrating to 1.19.0/latest image tags.
...