nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Burgess (Jira)" <>
Subject [jira] [Updated] (MINIFI-422) Incorporate MiNiFi Java functionality as a specialized assembly of NiFI
Date Wed, 28 Apr 2021 16:12:00 GMT


Matt Burgess updated MINIFI-422:
    Fix Version/s: 1.14.0

> Incorporate MiNiFi Java functionality as a specialized assembly of NiFI 
> ------------------------------------------------------------------------
>                 Key: MINIFI-422
>                 URL:
>             Project: Apache NiFi MiNiFi
>          Issue Type: Task
>            Reporter: Aldrin Piri
>            Assignee: Matt Burgess
>            Priority: Major
>             Fix For: 1.14.0
>          Time Spent: 5h 10m
>  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
> 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

View raw message