You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Rene Weidlinger (Jira)" <ji...@apache.org> on 2021/03/30 15:04:00 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=17311568#comment-17311568 ]
Rene Weidlinger commented on MINIFI-422:
----------------------------------------
Danke für Ihre Nachricht!
Ich bin am Montag, 06.04.2021 wieder im Büro.
Ihre Emails werden nicht automatisch weitergeleitet.
Beste Grüße,
Rene Weidlinger
> 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
> Assignee: Matt Burgess
> Priority: Major
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> 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
(v8.3.4#803005)