Download nifi-lookup-service-api JAR file with all dependencies
nifi-site-to-site-client from group org.apache.nifi (version 1.4.0)
nifi-utils from group org.apache.nifi (version 1.7.0)
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.
3 downloads
nifi-processor-bundle-archetype from group org.apache.nifi (version 1.4.0)
nifi-flowfile-packager from group org.apache.nifi (version 1.4.0)
nifi-toolkit-tls from group org.apache.nifi (version 1.2.0)
Tooling to make tls configuration easier
3 downloads
nifi-record from group org.apache.nifi (version 1.4.0)
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.
3 downloads
nifi-toolkit-zookeeper-migrator from group org.apache.nifi (version 1.1.2)
nifi-security-utils from group org.apache.nifi (version 1.2.0)
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.
3 downloads
nifi-bootstrap from group org.apache.nifi (version 1.5.0)
3 downloads
nifi-utils from group org.apache.nifi (version 1.1.2)
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.
3 downloads
nifi-windows-event-log-processors from group org.apache.nifi (version 1.4.0)
nifi-flowfile-packager from group org.apache.nifi (version 1.7.1)
nifi-spark-receiver from group org.apache.nifi (version 1.6.0)
3 downloads
nifi-jetty from group org.apache.nifi (version 1.8.0)
3 downloads
nifi-mongodb-processors from group org.apache.nifi (version 1.8.0)
Page 3 from 22 (items total 328)
© 2015 - 2025 Weber Informatics LLC | Privacy Policy