NissimShiman commented on PR #6035:
URL: https://github.com/apache/nifi/pull/6035#issuecomment-1123915097
As this change touches a wide range of apache nifi core files/functionality,
extensive edge testing was done to verify the integrity of this new
functionality, especially with regards to backward compatibility with flow
configurations from apache nifi 1.16.x where this functionality does not exist.
flow.xml.gz / flow.json.xml from earlier versions can be dropped into the
conf directory and on nifi restart, any controller services in these files will
have tags added to reflect a bulletinLevel at the WARN level (to maintain
backward compatibility where WARN was previously globally set [1])
Templates from previous nifi versions can be used and nifi will start up and
will modify any controller services in these files (and their definitions in
the flow.xml.gz/flow.json.gz) to have a bulletinLevel at the WARN level
nifi-registry (on 1.17 and later) can be updated using flow_storage and
database directories from registries of 1.16.x and controller services in
flows that are brought over will have bulletinLevel set at WARN level. Their
definitions in the flow.xml.gz/flow.json.gz will be gracefully updated to
reflect this. The registry will also remain "up to date" at the latest version
when this done as well.
[1]
https://github.com/apache/nifi/blob/rel/nifi-1.16.1/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/flow/StandardFlowManager.java#L489-L490
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
