Re: MiNiFi Java -> NiFi
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 wrote: > Way to GO!!! This is awesome stuff. > > > Steven Matison | Data Architect > Mobile 321.848.4926 > steven.mati...@datastax.com | datastax.com > > > On Apr 28, 2021, at 2:08 PM, Matt Burgess 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
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 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.mati...@datastax.com> > wrote: > > > Way to GO!!! This is awesome stuff. > > > > > > Steven Matison | Data Architect > > Mobile 321.848.4926 > > steven.mati...@datastax.com | datastax.com > > > > > On Apr 28, 2021, at 2:08 PM, Matt Burgess > 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
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 alopre...@apache.org alopresto.apa...@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 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 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.mati...@datastax.com> >> wrote: >> >>> Way to GO!!! This is awesome stuff. >>> >>> >>> Steven Matison | Data Architect >>> Mobile 321.848.4926 >>> steven.mati...@datastax.com | datastax.com >>> On Apr 28, 2021, at 2:08 PM, Matt Burgess >> 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: Issue uploading Nifi templates via UI and curl, NiFi 1.13.2 and up
Tim, I've seen this behavior as well, I wrote up [1] to track it in Jira. Regards, Matt [1] https://issues.apache.org/jira/browse/NIFI-8496 On Wed, Apr 28, 2021 at 12:40 PM Smith, Tim wrote: > > Started receiving HTTP 500 internal server errors when attempting to upload > template through UI after upgarding to version 1,13,2. Related, unable to > utilize the nifi-api REST interface to upload templates as well. > > > In both cases, template is uploaded but return failed responses. This did not > occur in NiFi 1.12 > > Last testing performed 1.14 snapshot in my fork. > > > Errors in nifi log after curl : > > Caused by: > org.glassfish.jersey.message.internal.MessageBodyProviderNotFoundException: > MessageBodyWriter not found for media type=application/xml, type=class > org.apache.nifi.web.api.entity.TemplateEntity, genericType=class > org.apache.nifi.web.api.entity.TemplateEntity. > > Has this already been reported? > > Tim Smith > >
Issue uploading Nifi templates via UI and curl, NiFi 1.13.2 and up
Started receiving HTTP 500 internal server errors when attempting to upload template through UI after upgarding to version 1,13,2. Related, unable to utilize the nifi-api REST interface to upload templates as well. In both cases, template is uploaded but return failed responses. This did not occur in NiFi 1.12 Last testing performed 1.14 snapshot in my fork. Errors in nifi log after curl : Caused by: org.glassfish.jersey.message.internal.MessageBodyProviderNotFoundException: MessageBodyWriter not found for media type=application/xml, type=class org.apache.nifi.web.api.entity.TemplateEntity, genericType=class org.apache.nifi.web.api.entity.TemplateEntity. Has this already been reported? Tim Smith
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
Awesome Job Matt! > On Apr 28, 2021, at 14:08, Matt Burgess 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
Way to GO!!! This is awesome stuff. Steven Matison | Data Architect Mobile 321.848.4926 steven.mati...@datastax.com | datastax.com > On Apr 28, 2021, at 2:08 PM, Matt Burgess 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
