...

Migrating to 2.0.0

...

• Custom Components with Property Descriptor Builders passing null to the defaultValue() method are no longer supported

...

-M2

Migrating to 2.0.0-M1 M2 requires upgrading to 1.2425.0 prior to moving to 2.0.0-M1M2.

Version 2.0.0-M1 M2 is the first second milestone version of Apache NiFi 2.0.0. This version includes over 900 issues resolved, including new features as well as numerous improvements and bug fixes.

Please refer to the Deprecated Components and Features documentation for items removed in this version.Migrating Deprecated Components and Features for

In addition to the changes from 2.0.0-M1, version 2.0.0 includes current progress on the steps necessary for migrating certain components and features.-M2 includes several additional changes that may require manual adjustments when upgrading.

Deployment and Configuration Changes

• JoltTransformJSON and JoltTransformRecord moved to new nifi-jolt-nar
• Removed InfluxDB Processors
• Removed Bootstrap Notification Services
• Removed MiNiFi C2 Server
• Moved from SimpleDateFormat to DateTimeFormatter for date and time parsing and formatting

Custom Component Changes

• Custom Components with Property Descriptor Builders passing null to the defaultValue() method are no longer supported
• Upgrading from Servlet API 3 to Servlet API 6 requires changes from javax.servlet packages to jakarta.servlet packages

Migrating to 2.0.0-M1

Migrating to 2.0.0-M1 requires upgrading to 1.24.0 prior to moving to 2.0.0-M1.

Version 2.0.0-M1 is the first milestone version of Apache NiFi 2.0.0. This version includes over 900 issues resolved, including new features as well as numerous improvements and bug fixes.

Please refer to the Deprecated Components and Features documentation for items removed in this version.

Migrating Deprecated Components and Features for 2.0.0 includes current progress on the steps necessary for migrating certain components and features.

• The nifi.flow.configuration.file property in nifi.properties must be changed to reference flow.json.gz instead of flow.xml.gz
• The default bootstrap configuration no longer includes java.net.preferIPv4Stack=true as part of the standard settings. Systems that support IPv6 may require adjustments to host resolution settings.
• The ExpressionLanguageScope VARIABLE_REGISTRY has been removed.  An alternate expression language scope ENVIRONMENT is now available, allowing for similar configurability via JVM system properties or system environment variables.

Migrating to 1.24.0

• URL properties specified in components should be URL-encoded. NIFI-12103 NIFI-12513
  • InvokeHTTP (property HTTP URL)
  The nifi.flow.configuration.file property in nifi.properties must be changed to reference flow.json.gz instead of flow.xml.gz

Migrating to 1.23.0

• The resolution for CVE-2023-36542 included the addition of a new Access Policy component restriction named Reference Remote Resources applied to the following components:
  • CaptureChangeMySQL
  • ConsumeJMS
  • DBCPConnectionPool
  • ExtractGrok
  • GrokReader
  • HikariCPConnectionPool
  • HadoopDBCPConnectionPool
  • HBase_2_ClientService
  • JMSConnectionFactoryProvider
  • PublishJMS
  • ValidateJson
  • ValidateXml
• Deployments with fine-grained Access Policies may require assigning the Reference Remote Resources permission to users who should be able to configure applicable components
• The nifi-riemann-nar and nifi-hbase_1_1_2-client-service-nar are no longer included in the standard binary, but can be downloaded from Maven Central
• RethinkDB Processors are deprecated for removal in 2.0.0
• Upgrading dependencies from H2 Database Engine version 2.1 to 2.2 required internal automated migration

...

• DBCPConnectionPool and HikariCPConnectionPool Controller Services no longer support H2 database connections according to Database URL validation added in NIFI-11653
• JndiJmsConnectionFactoryProvider Controller Service along with ConsumeJMS and PublishJMS Processors no longer support LDAP Provider URLs according to validation added in NIFI-11614
  • The additional details documentation for JndiJmsConnectionFactoryProvider describes an optional Java System property that can be added to bootstrap.conf to enable LDAP for specific use cases
• GetAzureQueueStorage and PutAzureQueueStorage have been deprecated in favor of GetAzureQueueStorage_v12 and PutAzureQueueStorage_v12
• ECMAScript, lua, and ruby have been deprecated for Scripted components in favor of Groovy
• GetIgniteCache and PutIgniteCache have been deprecated for removal in 2.0.0
• The Compression Type property has been removed from AbstractCassandraProcessor which affects PutCassandraQL, PutCassandraRecord, and QueryCassandra. This will cause existing instances of these processors to become invalid. To migrate the flow, remove that property which is now displayed as an unsupported property in the processors' configuration dialogs. If a Compression Type other than the default "NONE" is needed, use a Cassandra Connection Provider controller service rather than the direct properties in the processor. (NIFI-5642)

Migrating to 1.21.0

• Refactored OpenID Connect integration changed the Post Logout Redirect URI to avoid using relative paths
  • Previous Post Logout Redirect URI Path: /nifi-api/../nifi/logout-complete
  • New Post Logout Redirect URI Path: /nifi/logout-complete
  • OpenID Connect Identity Providers that support RP-Initiated Logout 1.0 may need to be updated with the new Post Logout Redirect URI
• Refactored OpenID Connect integration changed application Bearer Token expiration to derive from the Access Token instead of the ID Token
  • Some Identity Providers return the same expiration for both Access Tokens and ID Tokens, but providers that support different values may need to be updated so that the Access Token reflects the expected application session expiration

...