[
https://issues.apache.org/jira/browse/MINIFI-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16834758#comment-16834758
]
Aldrin Piri commented on MINIFI-422:
------------------------------------
Hi [~JPercivall]!
I have a few branches that are working on aspects of this that I haven't been
able to fully get instrumented with tests and such in NiFi. These are
https://github.com/apiri/incubator-nifi/commits/MINIFI-488 &
https://github.com/apiri/incubator-nifi/commits/MINIFI-485.
MINIFI-488 a proof of concept startup of NiFi from a YAML config and certainly
needs some adjustment but covers the base approach to make it work.
My mental model is to incorporate some of the outstanding items into MiNiFi for
one more release (although based on 1.8.x given the difficulties highlighted in
494) and work on some modularity to better compose items to port over to NiFi.
At that point, update perform the transition targeting 1.10 carrying out the
list of tasks encompassed in this ticket. If you are interested in getting
involved in any of these steps let me know and am happy to collaborate to move
things ahead a bit more. Have been a bit busy with other tasking and items.
> Incorporate MiNiFi Java functionality as a specialized assembly of NiFI
> ------------------------------------------------------------------------
>
> Key: MINIFI-422
> URL: https://issues.apache.org/jira/browse/MINIFI-422
> Project: Apache NiFi MiNiFi
> Issue Type: Task
> Reporter: Aldrin Piri
> Priority: Major
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
