Unsupported features

The following features are developed and tested by the Cloudera community but are not officially supported by Cloudera. These features are excluded for a variety of reasons, including insufficient reliability or incomplete test case coverage, declaration of non-production readiness by the community at large, and feature deviation from Cloudera best practices. Do not use these features in your production environments.

Unsupported NiFi components

NARs

NiFi 1 custom NARs cannot be successfully loaded into NiFi 2. If your NiFi setup includes custom NARs, it is a requirement to update your dependencies to align with NiFi 2. This entails making the necessary adjustments and rebuilding your NARs using Java 21. The below components are not supported and should not be used anymore.

  • nifi-cybersecurity-nar
  • nifi-email-nar
  • nifi-hive-nar
  • nifi-rethinkdb-nar
  • nifi-influxdb-nar
  • nifi-ccda-nar
  • nifi-html-nar
  • nifi-ignite-nar
  • nifi-tcp-nar
  • nifi-riemann-nar
  • nifi-spring-nar
  • nifi-kite-nar
  • nifi-rules-action-handler-nar
  • nifi-azure-nar
  • nifi-easyrules-nar
  • nifi-metrics-reporting-nar
  • nifi-other-graph-services-nar
  • nifi-hbase_1_1_2-client-service-nar
  • nifi-scripting-nar
  • nifi-ambari-nar
  • nifi-sql-reporting-nar
  • nifi-aws-nar
  • nifi-accumulo-nar
  • nifi-solr-nar
  • nifi-accumulo-service-nar
  • nifi-datadog-nar
  • nifi-atlas-nar
  • nifi-beats-nar
  • nifi-standard-nar
  • nifi-language-translation-nar
  • nifi-livy-nar
  • nifi-pulsar-nar

Rules engine processors

Rules engine components and handlers are removed in NiFi 2, so the below processors are not supported and should not be used anymore.

  • ActionHandlerLookup
  • AlertHandler
  • EasyRulesEngineProvider
  • EasyRulesEngineService
  • ExpressionHandler
  • LogHandler
  • RecordSinkHandler
  • ScriptedActionHandler
  • ScriptedRulesEngine

Unsupported customizations

Cloudera cannot guarantee that default NiFi processors are compatible with proprietary protocol implementations or proprietary interface extensions. For example, Cloudera supports interfaces like JMS and JDBC that are built around standards, specifications, or open protocols, but does not support customizations of those interfaces, or proprietary extensions built on top of those interfaces.