Group: org.apache.nifi - All Dependencies

This nifi-utils module should be a general purpose place to store widely and generally useful functions that any component might want to leverage. NO DEPENDENCIES should be added. This module is likely to be leveraged by every extension and should not bring along any other dependencies. The only dependency intended is the nifi-api and even this is expected to be already provided in any case where it would be used. The typical place this util would be found is within a nar and all nars already have nifi-api as a parent dependency. The nifi-api can be thought of as a NiFi Application Container level dependency.

This nifi-processor-utils module is designed to capture common patterns and utilities that can be leveraged by other processors or components to help promote reuse. These patterns may become framework level features or may simply be made available through this utility. It is ok for this module to have dependencies but care should be taken when adding dependencies as this increases the cost of utilizing this module in various nars.

This module contains the domain model for NiFi's Record abstraction, including several interfaces for interacting with Records. This module should not depend on any external libraries.

This nifi-security-utils module is meant to hold the majority of utilities that one could need to enable secure transport or interact with encryption. Care should be taken to keep the number of dependencies to a minimum given the utility nature of this library.

Provides an API for a Client that interfaces with a Distributed Cache