...
- 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.