Description
At its core the Java implementation of MiNiFi has largely been a core body of NiFi core libraries in a separate assembly with some additional extension points, namely those of configuration (via YAML) and configuration change listeners.
Due to working with some of the internals of NiFi that are not exactly meant for external consumption, there has been a certain impedance with each successive release to make use of the latest and greatest.
This ticket is to investigate and consider the incorporation of MiNiFi Java into the NiFi code base in a manner as highlighted above, extending/adapting the core libraries, providing some additional extension points, and then generating a custom assembly.
The idea is that in lieu of duplicating bits of code and providing workarounds around some of the internal APIs we can have a more streamlined build and keep these items in lockstep with the core NiFi libraries being more aware of changes that MiNiFi is inherently dependent upon.
To our users, there should be little perceptible change. The core means of interaction should remain while providing a similar footprint.
Attachments
Issue Links
- contains
-
NIFI-6813 Add C&C server Connector
- Open
-
NIFI-8565 Create FlowController implementation
- Open
- duplicates
-
MINIFI-540 Write nifi.kerberos.krb5.file to nifi.properties
- Resolved
- fixes
-
MINIFI-481 Update to use new handling of ExtensionManager
- Resolved
-
MINIFI-494 Update NiFi dependency to 1.9.0
- Resolved
- is related to
-
NIFI-8569 Consider common dependency management with NiFi
- Resolved
- relates to
-
MINIFI-429 Unable to use SSL Context with ListenHTTP
- Resolved
- supercedes
-
MINIFI-476 Release 0.6.0
- Resolved
- links to
1.
|
Allow provenance indexing to be disabled and associated dependencies excluded from builds | Open | Unassigned | |
2.
|
Support change ingestors | In Progress | Aldrin Piri | |
3.
|
Migrate documentation | Open | Unassigned |