You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nifi.apache.org by Matt Burgess <ma...@apache.org> on 2021/04/28 18:08:45 UTC
MiNiFi Java -> NiFi
All,
Now that [1] is merged, MiNiFi Java is now officially in the NiFi
codebase! Thanks to all who participated in discussions, reviews, and
testing. Here are some notes on what this means going forward:
- All future releases of MiNiFi Java will be in lockstep with NiFi,
the next release version will be 1.14.0 rather than 0.6.0. MiNiFi Java
artifacts will be built and published as part of the NiFi release
process. This will allow MiNiFi to immediately benefit from
improvements/fixes in NiFi components instead of occasionally updating
the NiFi dependency version in MiNiFi Java.
- Although we will continue to track issues in Jira under the MINIFI
project, PRs should be submitted against the nifi repo's main branch.
If you have an open PR against the nifi-minifi repo, you can port it
to the nifi repo by adding ".patch" to the URL of your PR, downloading
the patch, and applying it to a branch in your fork of the nifi repo,
for example:
git checkout -b MINIFI-541
git apply --directory='minifi' ~/195.patch
Sooner than later we'll make the nifi-minifi repo read-only so no more
PRs can be submitted against it, and we can update NiFi's PR template
to refer to MINIFI Jira cases as well.
There's still work to be done of course, contributions and PR reviews
are most welcome!
Regards,
Matt
[1] https://github.com/apache/nifi/pull/4933
Re: MiNiFi Java -> NiFi
Posted by Chad Zobrisky <cz...@gmail.com>.
Matt,
This is awesome! Thank you for all the work you and others have done to get
minifi into the Nifi baseline!
I've been following this since the beginning and look forward to trying
this out and all the benefits it will bring to minifi!
On Thu, Apr 29, 2021 at 12:22 AM Andy LoPresto <al...@gmail.com>
wrote:
> Matt, this is awesome work and so much of it is invisible to the average
> eye. Congratulations and thank you for doing this.
>
> Andy LoPresto
> alopresto@apache.org
> alopresto.apache@gmail.com
> He/Him
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
>
> > On Apr 28, 2021, at 16:34, Joe Witt <jo...@gmail.com> wrote:
> >
> > Was thinking the same thing. Id advocate we ditch the minifi jira
> project.
> > Just have minifi as a component if nifi jira
> >
> > Thanks
> >
> >> On Wed, Apr 28, 2021 at 3:45 PM Aldrin Piri <al...@apache.org> wrote:
> >>
> >> Awesome work, Matt!
> >>
> >> In terms of project management, is there any merit in maintaining the
> >> MINIFI tracker after the merge is complete versus using components?
> >> Do you envision subtree releases off the nifi repo for minifi
> specifically?
> >>
> >> On Wed, Apr 28, 2021 at 11:17 AM Steven Matison <
> >> steven.matison@datastax.com>
> >> wrote:
> >>
> >>> Way to GO!!! This is awesome stuff.
> >>>
> >>>
> >>> Steven Matison | Data Architect
> >>> Mobile 321.848.4926
> >>> steven.matison@datastax.com | datastax.com
> >>>
> >>>> On Apr 28, 2021, at 2:08 PM, Matt Burgess <ma...@apache.org>
> >> wrote:
> >>>>
> >>>> All,
> >>>>
> >>>> Now that [1] is merged, MiNiFi Java is now officially in the NiFi
> >>>> codebase! Thanks to all who participated in discussions, reviews, and
> >>>> testing. Here are some notes on what this means going forward:
> >>>>
> >>>> - All future releases of MiNiFi Java will be in lockstep with NiFi,
> >>>> the next release version will be 1.14.0 rather than 0.6.0. MiNiFi Java
> >>>> artifacts will be built and published as part of the NiFi release
> >>>> process. This will allow MiNiFi to immediately benefit from
> >>>> improvements/fixes in NiFi components instead of occasionally updating
> >>>> the NiFi dependency version in MiNiFi Java.
> >>>>
> >>>> - Although we will continue to track issues in Jira under the MINIFI
> >>>> project, PRs should be submitted against the nifi repo's main branch.
> >>>> If you have an open PR against the nifi-minifi repo, you can port it
> >>>> to the nifi repo by adding ".patch" to the URL of your PR, downloading
> >>>> the patch, and applying it to a branch in your fork of the nifi repo,
> >>>> for example:
> >>>>
> >>>> git checkout -b MINIFI-541
> >>>> git apply --directory='minifi' ~/195.patch
> >>>>
> >>>> Sooner than later we'll make the nifi-minifi repo read-only so no more
> >>>> PRs can be submitted against it, and we can update NiFi's PR template
> >>>> to refer to MINIFI Jira cases as well.
> >>>>
> >>>> There's still work to be done of course, contributions and PR reviews
> >>>> are most welcome!
> >>>>
> >>>> Regards,
> >>>> Matt
> >>>>
> >>>> [1] https://github.com/apache/nifi/pull/4933
> >>>
> >>>
> >>
>
Re: MiNiFi Java -> NiFi
Posted by Andy LoPresto <al...@gmail.com>.
Matt, this is awesome work and so much of it is invisible to the average eye. Congratulations and thank you for doing this.
Andy LoPresto
alopresto@apache.org
alopresto.apache@gmail.com
He/Him
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
> On Apr 28, 2021, at 16:34, Joe Witt <jo...@gmail.com> wrote:
>
> Was thinking the same thing. Id advocate we ditch the minifi jira project.
> Just have minifi as a component if nifi jira
>
> Thanks
>
>> On Wed, Apr 28, 2021 at 3:45 PM Aldrin Piri <al...@apache.org> wrote:
>>
>> Awesome work, Matt!
>>
>> In terms of project management, is there any merit in maintaining the
>> MINIFI tracker after the merge is complete versus using components?
>> Do you envision subtree releases off the nifi repo for minifi specifically?
>>
>> On Wed, Apr 28, 2021 at 11:17 AM Steven Matison <
>> steven.matison@datastax.com>
>> wrote:
>>
>>> Way to GO!!! This is awesome stuff.
>>>
>>>
>>> Steven Matison | Data Architect
>>> Mobile 321.848.4926
>>> steven.matison@datastax.com | datastax.com
>>>
>>>> On Apr 28, 2021, at 2:08 PM, Matt Burgess <ma...@apache.org>
>> wrote:
>>>>
>>>> All,
>>>>
>>>> Now that [1] is merged, MiNiFi Java is now officially in the NiFi
>>>> codebase! Thanks to all who participated in discussions, reviews, and
>>>> testing. Here are some notes on what this means going forward:
>>>>
>>>> - All future releases of MiNiFi Java will be in lockstep with NiFi,
>>>> the next release version will be 1.14.0 rather than 0.6.0. MiNiFi Java
>>>> artifacts will be built and published as part of the NiFi release
>>>> process. This will allow MiNiFi to immediately benefit from
>>>> improvements/fixes in NiFi components instead of occasionally updating
>>>> the NiFi dependency version in MiNiFi Java.
>>>>
>>>> - Although we will continue to track issues in Jira under the MINIFI
>>>> project, PRs should be submitted against the nifi repo's main branch.
>>>> If you have an open PR against the nifi-minifi repo, you can port it
>>>> to the nifi repo by adding ".patch" to the URL of your PR, downloading
>>>> the patch, and applying it to a branch in your fork of the nifi repo,
>>>> for example:
>>>>
>>>> git checkout -b MINIFI-541
>>>> git apply --directory='minifi' ~/195.patch
>>>>
>>>> Sooner than later we'll make the nifi-minifi repo read-only so no more
>>>> PRs can be submitted against it, and we can update NiFi's PR template
>>>> to refer to MINIFI Jira cases as well.
>>>>
>>>> There's still work to be done of course, contributions and PR reviews
>>>> are most welcome!
>>>>
>>>> Regards,
>>>> Matt
>>>>
>>>> [1] https://github.com/apache/nifi/pull/4933
>>>
>>>
>>
Re: MiNiFi Java -> NiFi
Posted by Matt Burgess <ma...@apache.org>.
Moving MINIFI Jira cases to the NIFI project works for me too, anyone
have any objections?
On Wed, Apr 28, 2021 at 7:34 PM Joe Witt <jo...@gmail.com> wrote:
>
> Was thinking the same thing. Id advocate we ditch the minifi jira project.
> Just have minifi as a component if nifi jira
>
> Thanks
>
> On Wed, Apr 28, 2021 at 3:45 PM Aldrin Piri <al...@apache.org> wrote:
>
> > Awesome work, Matt!
> >
> > In terms of project management, is there any merit in maintaining the
> > MINIFI tracker after the merge is complete versus using components?
> > Do you envision subtree releases off the nifi repo for minifi specifically?
> >
> > On Wed, Apr 28, 2021 at 11:17 AM Steven Matison <
> > steven.matison@datastax.com>
> > wrote:
> >
> > > Way to GO!!! This is awesome stuff.
> > >
> > >
> > > Steven Matison | Data Architect
> > > Mobile 321.848.4926
> > > steven.matison@datastax.com | datastax.com
> > >
> > > > On Apr 28, 2021, at 2:08 PM, Matt Burgess <ma...@apache.org>
> > wrote:
> > > >
> > > > All,
> > > >
> > > > Now that [1] is merged, MiNiFi Java is now officially in the NiFi
> > > > codebase! Thanks to all who participated in discussions, reviews, and
> > > > testing. Here are some notes on what this means going forward:
> > > >
> > > > - All future releases of MiNiFi Java will be in lockstep with NiFi,
> > > > the next release version will be 1.14.0 rather than 0.6.0. MiNiFi Java
> > > > artifacts will be built and published as part of the NiFi release
> > > > process. This will allow MiNiFi to immediately benefit from
> > > > improvements/fixes in NiFi components instead of occasionally updating
> > > > the NiFi dependency version in MiNiFi Java.
> > > >
> > > > - Although we will continue to track issues in Jira under the MINIFI
> > > > project, PRs should be submitted against the nifi repo's main branch.
> > > > If you have an open PR against the nifi-minifi repo, you can port it
> > > > to the nifi repo by adding ".patch" to the URL of your PR, downloading
> > > > the patch, and applying it to a branch in your fork of the nifi repo,
> > > > for example:
> > > >
> > > > git checkout -b MINIFI-541
> > > > git apply --directory='minifi' ~/195.patch
> > > >
> > > > Sooner than later we'll make the nifi-minifi repo read-only so no more
> > > > PRs can be submitted against it, and we can update NiFi's PR template
> > > > to refer to MINIFI Jira cases as well.
> > > >
> > > > There's still work to be done of course, contributions and PR reviews
> > > > are most welcome!
> > > >
> > > > Regards,
> > > > Matt
> > > >
> > > > [1] https://github.com/apache/nifi/pull/4933
> > >
> > >
> >
Re: MiNiFi Java -> NiFi
Posted by Joe Witt <jo...@gmail.com>.
Was thinking the same thing. Id advocate we ditch the minifi jira project.
Just have minifi as a component if nifi jira
Thanks
On Wed, Apr 28, 2021 at 3:45 PM Aldrin Piri <al...@apache.org> wrote:
> Awesome work, Matt!
>
> In terms of project management, is there any merit in maintaining the
> MINIFI tracker after the merge is complete versus using components?
> Do you envision subtree releases off the nifi repo for minifi specifically?
>
> On Wed, Apr 28, 2021 at 11:17 AM Steven Matison <
> steven.matison@datastax.com>
> wrote:
>
> > Way to GO!!! This is awesome stuff.
> >
> >
> > Steven Matison | Data Architect
> > Mobile 321.848.4926
> > steven.matison@datastax.com | datastax.com
> >
> > > On Apr 28, 2021, at 2:08 PM, Matt Burgess <ma...@apache.org>
> wrote:
> > >
> > > All,
> > >
> > > Now that [1] is merged, MiNiFi Java is now officially in the NiFi
> > > codebase! Thanks to all who participated in discussions, reviews, and
> > > testing. Here are some notes on what this means going forward:
> > >
> > > - All future releases of MiNiFi Java will be in lockstep with NiFi,
> > > the next release version will be 1.14.0 rather than 0.6.0. MiNiFi Java
> > > artifacts will be built and published as part of the NiFi release
> > > process. This will allow MiNiFi to immediately benefit from
> > > improvements/fixes in NiFi components instead of occasionally updating
> > > the NiFi dependency version in MiNiFi Java.
> > >
> > > - Although we will continue to track issues in Jira under the MINIFI
> > > project, PRs should be submitted against the nifi repo's main branch.
> > > If you have an open PR against the nifi-minifi repo, you can port it
> > > to the nifi repo by adding ".patch" to the URL of your PR, downloading
> > > the patch, and applying it to a branch in your fork of the nifi repo,
> > > for example:
> > >
> > > git checkout -b MINIFI-541
> > > git apply --directory='minifi' ~/195.patch
> > >
> > > Sooner than later we'll make the nifi-minifi repo read-only so no more
> > > PRs can be submitted against it, and we can update NiFi's PR template
> > > to refer to MINIFI Jira cases as well.
> > >
> > > There's still work to be done of course, contributions and PR reviews
> > > are most welcome!
> > >
> > > Regards,
> > > Matt
> > >
> > > [1] https://github.com/apache/nifi/pull/4933
> >
> >
>
Re: MiNiFi Java -> NiFi
Posted by Aldrin Piri <al...@apache.org>.
Awesome work, Matt!
In terms of project management, is there any merit in maintaining the
MINIFI tracker after the merge is complete versus using components?
Do you envision subtree releases off the nifi repo for minifi specifically?
On Wed, Apr 28, 2021 at 11:17 AM Steven Matison <st...@datastax.com>
wrote:
> Way to GO!!! This is awesome stuff.
>
>
> Steven Matison | Data Architect
> Mobile 321.848.4926
> steven.matison@datastax.com | datastax.com
>
> > On Apr 28, 2021, at 2:08 PM, Matt Burgess <ma...@apache.org> wrote:
> >
> > All,
> >
> > Now that [1] is merged, MiNiFi Java is now officially in the NiFi
> > codebase! Thanks to all who participated in discussions, reviews, and
> > testing. Here are some notes on what this means going forward:
> >
> > - All future releases of MiNiFi Java will be in lockstep with NiFi,
> > the next release version will be 1.14.0 rather than 0.6.0. MiNiFi Java
> > artifacts will be built and published as part of the NiFi release
> > process. This will allow MiNiFi to immediately benefit from
> > improvements/fixes in NiFi components instead of occasionally updating
> > the NiFi dependency version in MiNiFi Java.
> >
> > - Although we will continue to track issues in Jira under the MINIFI
> > project, PRs should be submitted against the nifi repo's main branch.
> > If you have an open PR against the nifi-minifi repo, you can port it
> > to the nifi repo by adding ".patch" to the URL of your PR, downloading
> > the patch, and applying it to a branch in your fork of the nifi repo,
> > for example:
> >
> > git checkout -b MINIFI-541
> > git apply --directory='minifi' ~/195.patch
> >
> > Sooner than later we'll make the nifi-minifi repo read-only so no more
> > PRs can be submitted against it, and we can update NiFi's PR template
> > to refer to MINIFI Jira cases as well.
> >
> > There's still work to be done of course, contributions and PR reviews
> > are most welcome!
> >
> > Regards,
> > Matt
> >
> > [1] https://github.com/apache/nifi/pull/4933
>
>
Re: MiNiFi Java -> NiFi
Posted by Steven Matison <st...@datastax.com>.
Way to GO!!! This is awesome stuff.
Steven Matison | Data Architect
Mobile 321.848.4926
steven.matison@datastax.com | datastax.com
> On Apr 28, 2021, at 2:08 PM, Matt Burgess <ma...@apache.org> wrote:
>
> All,
>
> Now that [1] is merged, MiNiFi Java is now officially in the NiFi
> codebase! Thanks to all who participated in discussions, reviews, and
> testing. Here are some notes on what this means going forward:
>
> - All future releases of MiNiFi Java will be in lockstep with NiFi,
> the next release version will be 1.14.0 rather than 0.6.0. MiNiFi Java
> artifacts will be built and published as part of the NiFi release
> process. This will allow MiNiFi to immediately benefit from
> improvements/fixes in NiFi components instead of occasionally updating
> the NiFi dependency version in MiNiFi Java.
>
> - Although we will continue to track issues in Jira under the MINIFI
> project, PRs should be submitted against the nifi repo's main branch.
> If you have an open PR against the nifi-minifi repo, you can port it
> to the nifi repo by adding ".patch" to the URL of your PR, downloading
> the patch, and applying it to a branch in your fork of the nifi repo,
> for example:
>
> git checkout -b MINIFI-541
> git apply --directory='minifi' ~/195.patch
>
> Sooner than later we'll make the nifi-minifi repo read-only so no more
> PRs can be submitted against it, and we can update NiFi's PR template
> to refer to MINIFI Jira cases as well.
>
> There's still work to be done of course, contributions and PR reviews
> are most welcome!
>
> Regards,
> Matt
>
> [1] https://github.com/apache/nifi/pull/4933
Re: MiNiFi Java -> NiFi
Posted by Otto Fowler <ot...@gmail.com>.
Awesome Job Matt!
> On Apr 28, 2021, at 14:08, Matt Burgess <ma...@apache.org> wrote:
>
> All,
>
> Now that [1] is merged, MiNiFi Java is now officially in the NiFi
> codebase! Thanks to all who participated in discussions, reviews, and
> testing. Here are some notes on what this means going forward:
>
> - All future releases of MiNiFi Java will be in lockstep with NiFi,
> the next release version will be 1.14.0 rather than 0.6.0. MiNiFi Java
> artifacts will be built and published as part of the NiFi release
> process. This will allow MiNiFi to immediately benefit from
> improvements/fixes in NiFi components instead of occasionally updating
> the NiFi dependency version in MiNiFi Java.
>
> - Although we will continue to track issues in Jira under the MINIFI
> project, PRs should be submitted against the nifi repo's main branch.
> If you have an open PR against the nifi-minifi repo, you can port it
> to the nifi repo by adding ".patch" to the URL of your PR, downloading
> the patch, and applying it to a branch in your fork of the nifi repo,
> for example:
>
> git checkout -b MINIFI-541
> git apply --directory='minifi' ~/195.patch
>
> Sooner than later we'll make the nifi-minifi repo read-only so no more
> PRs can be submitted against it, and we can update NiFi's PR template
> to refer to MINIFI Jira cases as well.
>
> There's still work to be done of course, contributions and PR reviews
> are most welcome!
>
> Regards,
> Matt
>
> [1] https://github.com/apache/nifi/pull/4933