Versions Compared

Old Version 9

changes.mady.by.user Joe Witt

Saved on

compared with

New Version 10

changes.mady.by.user Joe Witt

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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 we don't know what to expect yet either (wink).  There there may be significant 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.MORE COMING SOON - 0.2.0 release is in development as of June 2015