THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
The Apache NiFi community recognizes how important it is to provide reliable releases on a number of levels. But one of the most important aspects is that we consider the importance of changes which create new behavior, change existing behavior and so on. We're committed to being a responsible community whereby we can continue to evolve the capabilities and features of NiFi and users can have a well understood and reliable upgrade path. We're committed to ensuring backward compatibility issues are made quite rare or that the impact is clearly understood, minimized, and communicated. You can read more about our approach to version management. If you find that we've violated this commitment in any way please send us an email at dev@nifi.apache.org and we'll work to resolve it for you and other users.
To summarize:
- 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 there may be backward compatibility impacting changes largely focused on removal of deprecated items.
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 0.0.1 to 0.0.2
- There is now a content viewer available allowing you to look at content as it existed in the flow at certain stages as indexed with provenance. To enable this you must edit your 'conf/nifi.properties' file. Edit or add a line that says ''nifi.content.viewer.url=/nifi-content-viewer/"
- Migrating from 0.0.x to 0.1.0
- We have made management of controller services and reporting tasks a first-class feature that is manageable through the REST API and User Interface. This means that the 'conf/controller-services.xml' and 'conf/reporting-tasks.xml' are no longer going to be read in on startup. WARNING: You will have to recreate those services and tasks through the UI and you can delete those configuration files. This change is a violation of our commitment to proper compatibility changes (and what motivated this page in the first place).
- Migrating from 0.1.x to 0.2.0
- For Windows users: the start-nifi.bat and stop-nifi.bat have been removed. Please use run-nifi.bat instead. This was done in order to ensure that all messages from NiFi are properly written to the log files.
- Migrating from 0.2.0 to 0.3.0
- Added Reporting Tasks for integrating with Apache Ambari
- Added support for interacting with Kerberos enabled Hadoop clusters
- Added Processors that integrate with Amazon Web Services, processing images, execute SQL commands, run Apache Flume sources and sinks, and introduced additional avro capabilities.
- Archival of flow file content is now enabled by default with a target of 12 hours of retention or at 50% of total partition usage.