Versions Compared

Old Version 30

changes.mady.by.user Joe Witt

Saved on

compared with

New Version 31

changes.mady.by.user Joseph Percivall

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Adding migration for 1.0.0 to 1.0.1

...

  • Migrating from 1.0.x to 1.1.0
    • NiFi now supports the concept of restricted components.  These are processors, controller services, reporting tasks that allow an authorized user to execute unsanitized code or access and alter files accessible by the NiFi user on the system NiFi is running.  Therefore, these components are tagged by the developer as restricted and when running NiFi in secure mode only an administrator must grant each user access to the policy allowing restricted component access.  This is explained in greater detail in the admin, user, and developer guides.  When you upgrade you will need to give your users access to this policy to be able to use these components.
    • During cluster startup we have to determine which flow is going to be considered the correct flow to go on based on which nodes attempt to join the cluster.  To help speed up this process there are now two new nifi.properties keys and values you should consider.  They are "nifi.cluster.flow.election.max.wait.time" and "nifi.cluster.flow.election.max.candidates".  You can read more about this in the admin guide under "Flow Election".
  • Migrating from 1.0.0 to 1.0.1
    • No known migration issues.
  • Migrating from 0.7.x to 1.0.0
    • Java 8 is now the minimum JRE/JDK supported
      • Before NiFi 1.0 release we supported a minimum of Java 7.  We've now moved to Java 8.

...