Minifi updates

[Chad Zobrisky <cz...@gmail.com>]

Minifi is a few releases behind and was wondering if a new release was in
the works to base line it off of a more recent nifi version.

We were also looking for encrypted values for the expression language, is
it possible to start work on moving parameter contexts into the minifi
project? Any thoughts?

Thanks,
Chad

Re: Minifi updates

[Chad Zobrisky <cz...@gmail.com>]

Aldrin,

Definitely have been looking to contribute back and this seems like
something that would be pretty useful. Let me know where you are at and
where I can help.

Thanks,
Chad

On Fri, Feb 21, 2020 at 4:40 PM Aldrin Piri <al...@gmail.com> wrote:

> Hey Chad,
>
> Thanks for checking in.
>
> To the point, I think what behooves the community as a whole is to
> appropriately treat MiNiFi as an assembly of NiFi given its shared core and
> mitigate this dependent nature.  This effort and the work involved is
> largely encapsulated by the following tickets:
>
> * https://issues.apache.org/jira/browse/MINIFI-422 - Parent ticket to
> bring
> these capabilities to NiFi
> * https://issues.apache.org/jira/browse/MINIFI-436
> * https://issues.apache.org/jira/browse/MINIFI-494
> * https://issues.apache.org/jira/browse/MINIFI-481
>
> By no means is the way it has to be accomplished.  We could likely work a
> way out to get things upgraded as MINIFI-494 highlights, but being
> efficient with folks' efforts, I would lean toward us taking a bit longer
> and in lieu of putting time into duplicative, incremental maintenance.
> Outside of all of that, if either of these approaches seem like an area you
> might wish to get involved in, please feel free to drop a note on any of
> the linked issues and would be happy to collaborate.
>
> I have some additional thoughts that might take me a bit longer to compose
> and may deserve a separate thread.  I'll look to get those together and
> share them here for further consideration.
>
> --aldrin
>
> On Fri, Feb 21, 2020 at 4:17 PM Chad Zobrisky <cz...@gmail.com> wrote:
>
> > Minifi is a few releases behind and was wondering if a new release was in
> > the works to base line it off of a more recent nifi version.
> >
> > We were also looking for encrypted values for the expression language, is
> > it possible to start work on moving parameter contexts into the minifi
> > project? Any thoughts?
> >
> > Thanks,
> > Chad
> >
>

Re: Minifi updates

[Aldrin Piri <al...@gmail.com>]

Hey Chad,

Thanks for checking in.

To the point, I think what behooves the community as a whole is to
appropriately treat MiNiFi as an assembly of NiFi given its shared core and
mitigate this dependent nature.  This effort and the work involved is
largely encapsulated by the following tickets:

* https://issues.apache.org/jira/browse/MINIFI-422 - Parent ticket to bring
these capabilities to NiFi
* https://issues.apache.org/jira/browse/MINIFI-436
* https://issues.apache.org/jira/browse/MINIFI-494
* https://issues.apache.org/jira/browse/MINIFI-481

By no means is the way it has to be accomplished.  We could likely work a
way out to get things upgraded as MINIFI-494 highlights, but being
efficient with folks' efforts, I would lean toward us taking a bit longer
and in lieu of putting time into duplicative, incremental maintenance.
Outside of all of that, if either of these approaches seem like an area you
might wish to get involved in, please feel free to drop a note on any of
the linked issues and would be happy to collaborate.

I have some additional thoughts that might take me a bit longer to compose
and may deserve a separate thread.  I'll look to get those together and
share them here for further consideration.

--aldrin

On Fri, Feb 21, 2020 at 4:17 PM Chad Zobrisky <cz...@gmail.com> wrote:

> Minifi is a few releases behind and was wondering if a new release was in
> the works to base line it off of a more recent nifi version.
>
> We were also looking for encrypted values for the expression language, is
> it possible to start work on moving parameter contexts into the minifi
> project? Any thoughts?
>
> Thanks,
> Chad
>