THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
| Component Class | org.apache.nifi.processors.standard.Base64EncodeContent |
| Bundle Group | org.apache.nifi |
| Bundle Artifact | nifi-standard-nar |
| Deprecated Version | 1.20.0 |
| Migration Difficulty | LOW |
| Migration Type | Component Replacement |
Alternatives
| Component Class | org.apache.nifi.processors.standard.EncodeContent |
| Bundle Group | org.apache.nifi |
| Bundle Artifact | nifi-standard-nar |
...
GetHTTP
| Component Class | org.apache.nifi.processors.standard.GetHTTP |
| Bundle Group | org.apache.nifi |
| Bundle Artifact | nifi-standard-nar |
| Deprecated Version | 1.9.0 |
| Migration Difficulty | LOW |
| Migration Type | Component Replacement |
Alternatives
| Component Class | org.apache.nifi.processors.standard.InvokeHTTP |
| Bundle Group | org.apache.nifi |
| Bundle Artifact | nifi-standard-nar |
Migration
GetHTTP supports a number of configurable properties to retrieve data using the HTTP GET method. The URL property controls the primary behavior of the Processor.
GetHTTP requires the Filename property to set the corresponding FlowFile attribute for content retrieved. The Processor requires an SSL Context Service when the URL starts with the HTTPS scheme.
The standard InvokeHTTP Processor supports standard HTTP methods including GET. Unlike GetHTTP, InvokeHTTP does not require an SSL Context Service for accessing HTTPS locations as it defaults to the Java Runtime default certificate authorities.
InvokeHTTP has a required HTTP URL property and defaults to setting the FlowFile filename attribute to a random UUID. The filename attribute can be derived from the URL path using the Response FlowFile Naming Strategy property set to URL_PATH.
InvokeHTTP has lower default socket timeout settings than GetHTTP.
Setting standard InvokeHTTP properties provides functionality similar to GetHTTP,
| Property | Value |
|---|---|
| HTTP Method | GET |
| HTTP URL | HTTP or HTTPS location |
| Response FlowFile Naming Strategy | URL_PATH |
Flow Definitions
The Deprecated Flow Definition includes GetHTTP configured to retrieve the SHA-256 checksum for the NiFi 1.20.0 distribution. The Flow Definition also includes a required SSL Context Service configured with the Java Runtime cacerts Trust Store.
The Migrated Flow Definition includes InvokeHTTP configured with the same URL but without the SSL Context Service, which is not required for public trusted HTTPS services.
GetJMSQueue
| Component Class | org.apache.nifi.processors.standard.GetJMSQueue |
| Bundle Group | org.apache.nifi |
| Bundle Artifact | nifi-standard-nar |
| Deprecated Version | 1.3.0 |
| Migration Difficulty | MEDIUM |
| Migration Type | Component Replacement |
Alternatives
| Component Class | org.apache.nifi.processors.standard.ConsumeJMS |
| Bundle Group | org.apache.nifi |
| Bundle Artifact | nifi-standard-nar |
Migration
GetJMSQueue supports retrieving messages using the Java Message Service Queue interface to access Apache ActiveMQ.
The Processor bundles the ActiveMQ libraries and requires the URL property to specify the JMS server location, and the Destination Name property to specify the JMS queue for retrieval. Additional optional properties support TLS communication and authentication as well as batching.
The standard ConsumeJMS Processor similar functionality to GetJMSQueue, but requires additional configuration. ConsumeJMS does not bundle JMS libraries and requires referencing a local directory containing implementation JAR files.
ConsumeJMS should be configured with a Connection Factory Service implementation of JMSConnectionFactoryProvider with required properties. The ActiveMQ Artemis library provides the current supported version of JMS access.
| Property | Value |
|---|---|
| JMS Connection Factory Implementation Class | org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory |
| JMS Client Libraries | /opt/activemq-artemis-2.28.0/lib |
| JMS Broker URI | tcp://${AMQ_HOST}:61616 |
ConsumeJMS uses the Connection Factory Service along with several other properties to access JMS Queues.
| Property | Value |
|---|---|
| Connection Factory Service | JMSConnectionFactoryProvider |
| Destination Name | |
| Destination Type | QUEUE |
Flow Definitions
The Deprecated Flow Definition includes GetJMSQueue configured for ActiveMQ running on the localhost address with a specified Destination Name.
The Migrated Flow Definition includes ConsumeJMS configured with a JMSConnectionFactoryProvider using the same JMS broker information. The Migrated Flow Definition includes a JMS Parameters context with a Parameter named JmsClientLibrariesPath referencing the local directory containing the Apache ActiveMQ Artemis libraries.