...

Migrating from deprecated components and features requires different steps depending on configured properties. The level of difficulty varies based on the number of properties to be changed and the steps involved to maintain similar behavior.

Features

Migrating deprecated features requires changes to application properties or custom component implementations. The steps involved will be different based on implementation details and deployment use cases.

ProcessContext encrypt and decrypt methods

Migration

The ProcessContext interface provides property and component configuration information to Processors through the onTrigger method. The encrypt and decrypt methods supported enciphering and deciphering component-provided strings using the Sensitive Properties Key and Sensitive Properties Algorithm configured in nifi.properties.

These methods did not provide any persistent storage mechanism and also did not provide any guarantees of compatible behavior when changing application properties. Most components depend on framework capabilities to store and retrieve sensitive property values, obviating the need for these methods.

Custom components should use Property Descriptors with the sensitive field enabled to store and retrieve sensitive property values. Alternative uses of the encrypt and decrypt methods require custom implementation.

Processors

Migrating deprecated Processors and properties requires flow design changes. The steps required range from setting different property values to replacing one Processor with one or more Processors providing similar capabilities.

...

Migration

Base64EncodeContent supports a single Mode property that can be set to Encode or Decode.

...

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.

...

Migration

GetJMSQueue supports retrieving messages using the Java Message Service Queue interface to access Apache ActiveMQ.

...

Migration

GetJMSTopic supports retrieving messages using the Java Message Service Topic interface to access Apache ActiveMQ.

...

• GetJMSTopic-Migrated.json

GetTwitter

Alternatives

Migration

GetTwitter uses Version 1 of the Twitter REST API and relies on the retired Twitter Hosebird Client library.

...

Migration

HashAttribute supports generating an MD5 digest of one more FlowFile attribute name and value pairs. The MD5 algorithm is not secure for cryptographic operations, and alternatives such as the SHA-2 or SHA-3 algorithms should be used.

...

Migration

HashContent supports generating a digest of FlowFile content using a configurable algorithm and writing the hash to a specified FlowFile attribute.

...

Migration

InvokeHTTP includes several deprecated properties for configuring access through a proxy server.

...

Migration

PostHTTP supports sending FlowFile content to a configurable HTTP URL using the HTTP POST method.

...

Migration

PutJMS supports sending messages using the Java Message Service interface to access Apache ActiveMQ.

...