[
https://issues.apache.org/jira/browse/MINIFI-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16302199#comment-16302199
]
Aldrin Piri commented on MINIFI-422:
------------------------------------
[~JPercivall] Not sure of specifics but certainly could see a similar extension
based approach being compelling. Based on work I've done against such things
before, it certainly seems like a reasonably straightforward path but those are
always famous last words of any software endeavor :)
> 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
>
> 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
(v6.4.14#64029)
