You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Joseph Percivall (JIRA)" <ji...@apache.org> on 2019/05/07 09:41:01 UTC
[jira] [Commented] (MINIFI-422) Incorporate MiNiFi Java
functionality as a specialized assembly of NiFI
[ https://issues.apache.org/jira/browse/MINIFI-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16834573#comment-16834573 ]
Joseph Percivall commented on MINIFI-422:
-----------------------------------------
Hey [~aldrin], how are things going here? Taking a look at the comments in MiNiFi-494[1] and MiNFi-488[2] it appears there's progress still happening but I don't see git activity. Let me know if you want to bounce any ideas or have run into roadblocks that you could use help with.
[1] https://issues.apache.org/jira/browse/MINIFI-494
[2] https://issues.apache.org/jira/browse/MINIFI-488
> 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)