Re: [VOTE] Release Apache NiFi 1.5.0 (RC1)
+1 (binding) verified signature and hashes. built clean with contrib-check. ran some simple flows without issue. reviewed the NOTICE and LICENSE, saw no issues. On Wed, Jan 10, 2018 at 9:05 PM, Koji Kawamurawrote: > +1 (binding) Release this package as nifi-1.5.0 > > Verified signature and hashes. Built with include-atlas profile. > mvn clean install -Pcontrib-check,include-grpc,include-atlas > Confirmed flows using NiFi Registry and ReportLineageToAtlas reporting > task, worked as expected. > > On Thu, Jan 11, 2018 at 4:35 AM, Matt Gilman > wrote: > > +1 (binding) Release this package as nifi-1.5.0 > > > > Verified signature, hashes, build, etc. Ran through a number of scenarios > > with Apache NiFi Registry 0.1.0 and everything is working as expected. > > > > Thanks Joe for RMing this release! > > > > Matt > > > > On Wed, Jan 10, 2018 at 2:22 PM, Rob Moran wrote: > > > >> +1, non-binding > >> > >> * All looks good/in place following the release helper > >> * Reviewed help docs related to new Registry integration > >> * Connected a registry client and did some quick testing of basic > version > >> control related actions > >> > >> > >> On Wed, Jan 10, 2018 at 1:24 PM Andrew Lim > >> wrote: > >> > >> > +1 (non-binding) > >> > > >> > -Ran full clean install on OS X (10.11.6) > >> > -Tested integration with NiFi Registry > >> > -Ran record reader/writer flows > >> > -Reviewed resolved “Core UI” component Jiras and spot checked > inclusion > >> in > >> > build > >> > -Reviewed documentation > >> > > >> > Drew > >> > > >> > > >> > > On Jan 9, 2018, at 5:19 AM, Joe Witt wrote: > >> > > > >> > > Hello, > >> > > > >> > > I am pleased to be calling this vote for the source release of > Apache > >> > > NiFi nifi-1.5.0. > >> > > > >> > > The source zip, including signatures, digests, etc. can be found at: > >> > > https://repository.apache.org/content/repositories/ > orgapachenifi-1116 > >> > > > >> > > The Git tag is nifi-1.5.0-RC1 > >> > > The Git commit ID is 46d30c7e92f0ad034d9b35bf1d05c350ab5547ed > >> > > > >> > https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h= > >> 46d30c7e92f0ad034d9b35bf1d05c350ab5547ed > >> > > > >> > > Checksums of nifi-1.5.0-source-release.zip: > >> > > MD5: 046f2dde4af592dd8c05e55c2bbb3c4f > >> > > SHA1: 63b9a68b9f89200fd31f5561956a15b45b1b9c8c > >> > > SHA256: 40b155c4911414907835f2eb0d5a4d > a798935f27f1e5134218d904fe6c94 > >> 2d13 > >> > > > >> > > Release artifacts are signed with the following key: > >> > > https://people.apache.org/keys/committer/joewitt.asc > >> > > > >> > > KEYS file available here: > >> > > https://dist.apache.org/repos/dist/release/nifi/KEYS > >> > > > >> > > 195 issues were closed/resolved for this release: > >> > > > >> > https://issues.apache.org/jira/secure/ReleaseNote.jspa? > >> projectId=12316020=12341668 > >> > > > >> > > Release note highlights can be found here: > >> > > > >> > https://cwiki.apache.org/confluence/display/NIFI/ > >> Release+Notes#ReleaseNotes-Version1.5.0 > >> > > > >> > > The vote will be open for 72 hours. > >> > > Please download the release candidate and evaluate the necessary > items > >> > > including checking hashes, signatures, build > >> > > from source, and test. The please vote: > >> > > > >> > > [ ] +1 Release this package as nifi-1.5.0 > >> > > [ ] +0 no opinion > >> > > [ ] -1 Do not release this package because... > >> > > >> > > >> > >> -- > >> Rob > >> >
Re: [VOTE] Release Apache NiFi 1.5.0 (RC1)
+1 (binding) Release this package as nifi-1.5.0 Verified signature and hashes. Built with include-atlas profile. mvn clean install -Pcontrib-check,include-grpc,include-atlas Confirmed flows using NiFi Registry and ReportLineageToAtlas reporting task, worked as expected. On Thu, Jan 11, 2018 at 4:35 AM, Matt Gilmanwrote: > +1 (binding) Release this package as nifi-1.5.0 > > Verified signature, hashes, build, etc. Ran through a number of scenarios > with Apache NiFi Registry 0.1.0 and everything is working as expected. > > Thanks Joe for RMing this release! > > Matt > > On Wed, Jan 10, 2018 at 2:22 PM, Rob Moran wrote: > >> +1, non-binding >> >> * All looks good/in place following the release helper >> * Reviewed help docs related to new Registry integration >> * Connected a registry client and did some quick testing of basic version >> control related actions >> >> >> On Wed, Jan 10, 2018 at 1:24 PM Andrew Lim >> wrote: >> >> > +1 (non-binding) >> > >> > -Ran full clean install on OS X (10.11.6) >> > -Tested integration with NiFi Registry >> > -Ran record reader/writer flows >> > -Reviewed resolved “Core UI” component Jiras and spot checked inclusion >> in >> > build >> > -Reviewed documentation >> > >> > Drew >> > >> > >> > > On Jan 9, 2018, at 5:19 AM, Joe Witt wrote: >> > > >> > > Hello, >> > > >> > > I am pleased to be calling this vote for the source release of Apache >> > > NiFi nifi-1.5.0. >> > > >> > > The source zip, including signatures, digests, etc. can be found at: >> > > https://repository.apache.org/content/repositories/orgapachenifi-1116 >> > > >> > > The Git tag is nifi-1.5.0-RC1 >> > > The Git commit ID is 46d30c7e92f0ad034d9b35bf1d05c350ab5547ed >> > > >> > https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h= >> 46d30c7e92f0ad034d9b35bf1d05c350ab5547ed >> > > >> > > Checksums of nifi-1.5.0-source-release.zip: >> > > MD5: 046f2dde4af592dd8c05e55c2bbb3c4f >> > > SHA1: 63b9a68b9f89200fd31f5561956a15b45b1b9c8c >> > > SHA256: 40b155c4911414907835f2eb0d5a4da798935f27f1e5134218d904fe6c94 >> 2d13 >> > > >> > > Release artifacts are signed with the following key: >> > > https://people.apache.org/keys/committer/joewitt.asc >> > > >> > > KEYS file available here: >> > > https://dist.apache.org/repos/dist/release/nifi/KEYS >> > > >> > > 195 issues were closed/resolved for this release: >> > > >> > https://issues.apache.org/jira/secure/ReleaseNote.jspa? >> projectId=12316020=12341668 >> > > >> > > Release note highlights can be found here: >> > > >> > https://cwiki.apache.org/confluence/display/NIFI/ >> Release+Notes#ReleaseNotes-Version1.5.0 >> > > >> > > The vote will be open for 72 hours. >> > > Please download the release candidate and evaluate the necessary items >> > > including checking hashes, signatures, build >> > > from source, and test. The please vote: >> > > >> > > [ ] +1 Release this package as nifi-1.5.0 >> > > [ ] +0 no opinion >> > > [ ] -1 Do not release this package because... >> > >> > >> >> -- >> Rob >>
Re: Cross NAR Controller Service access with gradle
Aw, man! I spent my lunch hour getting the Gradle stuff going, just to learn there's already a plugin :) Thanks to @sponiro and to you for sharing! I will take a look to make sure it's up to date, but if it seems to be working for you, and you have access to the plugin through public repos (jcenter/bintray, maven central, etc.) then we might be better served with Pull Requests for any changes that are needed :) Regards, Matt On Wed, Jan 10, 2018 at 3:34 PM, Nicholas Deanewrote: > Awesome. Thanks, Matt! I was missing the dependency on the > nifi-standard-services-api-nar NAR. I spent some time looking things up and I > came across the gradle nar plugin [1] > > Using that plugin, my build.gradle now contains the following lines: > > compile "org.apache.nifi:nifi-ssl-context-service-api:$nifiVersion" > nar 'org.apache.nifi:nifi-standard-services-api-nar:1.4.0' > > Now when I build my custom nar, I can see that my processor requires the > SSLContextService from nifi-standard-services-api-nar. The > StandardSSLContextService from the default org.apache.nifi bundle shows up as > selectable in that property and I’m able to get the processor started up with > the SSLContext. > > [1] https://github.com/sponiro/gradle-nar-plugin > > Regards, > Nicholas > > On 2018-01-10, 3:25 PM, "Matt Burgess" wrote: > > Nicholas, > > I finally had a few cycles to iron out some bugs in the Gradle NAR > example [1], feel free to check it out as it should be in much better > shape. Once it's ready for primetime, I'd like to add it to Lazybones > [2] and/or find a home for it in nifi-maven [3] (or a new similar repo > nifi-gradle ;) > > I'm going to try to apply this to an existing NAR in the NiFi codebase > that does real work with third-party dependencies and parent NARs. > Eventually I'd like to see it building equivalently and way faster > than Maven :) > > Regards, > Matt > > [1] https://github.com/mattyb149/nifi-gradle-nar-example > [2] https://github.com/pledbrook/lazybones > [3] https://github.com/apache/nifi-maven > > On Tue, Jan 9, 2018 at 12:06 PM, Matt Burgess > wrote: > > Nicholas, > > > > You shouldn't need to reference StandardSSLContextService explicitly, > > as your processor should be using the interface SSLContextService > > only. In the Maven world, this is done by bringing in > > nifi-ssl-context-service-api as a "provided" dependency (not compile), > > and adding a dependency on your NAR module to the > > nifi-standard-services-api-nar NAR. This is handled by a custom > > NarMojo for doing NiFi ARchive (NAR) packaging [1]. > > > > In the Gradle world we'll need a task to do the same thing, I believe > > it is mostly a matter of getting the separate subprojects set up to > > mimic the Maven modules, and a task (whether published as a plugin > > like the NarMojo plugin is for Maven or not) to update the NAR > > manifest and such. I have begun work on this [2], please feel free to > > take a look and let me know what you think. At present I believe I am > > missing a directive to copy all the processors' subproject > > dependencies into the NAR output artifact, I think I know how to fix > > it (i.e. from project(':processors').tasks['jar'].archivePath) but > > haven't had time to try it out. > > > > Please let me know if you'd like to work on the Gradle stuff together, > > I would be happy to collaborate :) > > > > Regards, > > Matt > > > > [1] https://github.com/apache/nifi-maven > > [2] https://github.com/mattyb149/nifi-gradle-nar-example > > > > On Tue, Jan 9, 2018 at 11:47 AM, Nicholas Deane > wrote: > >> Hi, > >> > >> I’m working on a custom processor and want to utilize NiFi’s > SSLContextService. > >> > >> In my build.gradle dependencies section, I’ve included: > >> compile "org.apache.nifi:nifi-ssl-context-service-api:$nifiVersion" > >> > >> and in my code I’ve created the property descriptor with > .identifiesControllerService(SSLContextService.class) > >> > >> When I’m configuring the processor, I noticed that the property on the > processor says that it “Requires Controller Service: SSLContextService from > my-custom-nar”. When I create a StandardSSLContextService from the default > org.apache.nifi bundle, it doesn’t show up in the processor’s list (as > expected based on that info message). > >> > >> I tried bringing in “nifi-ssl-context-service” and now I have two > versions of StandardSSLContextService in the controller service list (one > from the org.apache.nifi bundle and the other from my-custom-nar bundle). Is > this how I should be doing something like this or is there a better way for > me to use Controller Services across bundles and
Re: Cross NAR Controller Service access with gradle
Awesome. Thanks, Matt! I was missing the dependency on the nifi-standard-services-api-nar NAR. I spent some time looking things up and I came across the gradle nar plugin [1] Using that plugin, my build.gradle now contains the following lines: compile "org.apache.nifi:nifi-ssl-context-service-api:$nifiVersion" nar 'org.apache.nifi:nifi-standard-services-api-nar:1.4.0' Now when I build my custom nar, I can see that my processor requires the SSLContextService from nifi-standard-services-api-nar. The StandardSSLContextService from the default org.apache.nifi bundle shows up as selectable in that property and I’m able to get the processor started up with the SSLContext. [1] https://github.com/sponiro/gradle-nar-plugin Regards, Nicholas On 2018-01-10, 3:25 PM, "Matt Burgess"wrote: Nicholas, I finally had a few cycles to iron out some bugs in the Gradle NAR example [1], feel free to check it out as it should be in much better shape. Once it's ready for primetime, I'd like to add it to Lazybones [2] and/or find a home for it in nifi-maven [3] (or a new similar repo nifi-gradle ;) I'm going to try to apply this to an existing NAR in the NiFi codebase that does real work with third-party dependencies and parent NARs. Eventually I'd like to see it building equivalently and way faster than Maven :) Regards, Matt [1] https://github.com/mattyb149/nifi-gradle-nar-example [2] https://github.com/pledbrook/lazybones [3] https://github.com/apache/nifi-maven On Tue, Jan 9, 2018 at 12:06 PM, Matt Burgess wrote: > Nicholas, > > You shouldn't need to reference StandardSSLContextService explicitly, > as your processor should be using the interface SSLContextService > only. In the Maven world, this is done by bringing in > nifi-ssl-context-service-api as a "provided" dependency (not compile), > and adding a dependency on your NAR module to the > nifi-standard-services-api-nar NAR. This is handled by a custom > NarMojo for doing NiFi ARchive (NAR) packaging [1]. > > In the Gradle world we'll need a task to do the same thing, I believe > it is mostly a matter of getting the separate subprojects set up to > mimic the Maven modules, and a task (whether published as a plugin > like the NarMojo plugin is for Maven or not) to update the NAR > manifest and such. I have begun work on this [2], please feel free to > take a look and let me know what you think. At present I believe I am > missing a directive to copy all the processors' subproject > dependencies into the NAR output artifact, I think I know how to fix > it (i.e. from project(':processors').tasks['jar'].archivePath) but > haven't had time to try it out. > > Please let me know if you'd like to work on the Gradle stuff together, > I would be happy to collaborate :) > > Regards, > Matt > > [1] https://github.com/apache/nifi-maven > [2] https://github.com/mattyb149/nifi-gradle-nar-example > > On Tue, Jan 9, 2018 at 11:47 AM, Nicholas Deane wrote: >> Hi, >> >> I’m working on a custom processor and want to utilize NiFi’s SSLContextService. >> >> In my build.gradle dependencies section, I’ve included: >> compile "org.apache.nifi:nifi-ssl-context-service-api:$nifiVersion" >> >> and in my code I’ve created the property descriptor with .identifiesControllerService(SSLContextService.class) >> >> When I’m configuring the processor, I noticed that the property on the processor says that it “Requires Controller Service: SSLContextService from my-custom-nar”. When I create a StandardSSLContextService from the default org.apache.nifi bundle, it doesn’t show up in the processor’s list (as expected based on that info message). >> >> I tried bringing in “nifi-ssl-context-service” and now I have two versions of StandardSSLContextService in the controller service list (one from the org.apache.nifi bundle and the other from my-custom-nar bundle). Is this how I should be doing something like this or is there a better way for me to use Controller Services across bundles and avoid having duplicates in that list? >> >> >> Notice - Confidential Information The information in this communication and any attachments is strictly confidential and intended only for the use of the individual(s) or entity(ies) named above. If you are not the intended recipient, any dissemination, distribution, copying or other use of the information contained in this communication and/or any attachment is strictly prohibited. If you have received this communication in error, please first notify the sender immediately and then delete this communication from all data storage devices and destroy all hard copies.
Re: Cross NAR Controller Service access with gradle
Nicholas, I finally had a few cycles to iron out some bugs in the Gradle NAR example [1], feel free to check it out as it should be in much better shape. Once it's ready for primetime, I'd like to add it to Lazybones [2] and/or find a home for it in nifi-maven [3] (or a new similar repo nifi-gradle ;) I'm going to try to apply this to an existing NAR in the NiFi codebase that does real work with third-party dependencies and parent NARs. Eventually I'd like to see it building equivalently and way faster than Maven :) Regards, Matt [1] https://github.com/mattyb149/nifi-gradle-nar-example [2] https://github.com/pledbrook/lazybones [3] https://github.com/apache/nifi-maven On Tue, Jan 9, 2018 at 12:06 PM, Matt Burgesswrote: > Nicholas, > > You shouldn't need to reference StandardSSLContextService explicitly, > as your processor should be using the interface SSLContextService > only. In the Maven world, this is done by bringing in > nifi-ssl-context-service-api as a "provided" dependency (not compile), > and adding a dependency on your NAR module to the > nifi-standard-services-api-nar NAR. This is handled by a custom > NarMojo for doing NiFi ARchive (NAR) packaging [1]. > > In the Gradle world we'll need a task to do the same thing, I believe > it is mostly a matter of getting the separate subprojects set up to > mimic the Maven modules, and a task (whether published as a plugin > like the NarMojo plugin is for Maven or not) to update the NAR > manifest and such. I have begun work on this [2], please feel free to > take a look and let me know what you think. At present I believe I am > missing a directive to copy all the processors' subproject > dependencies into the NAR output artifact, I think I know how to fix > it (i.e. from project(':processors').tasks['jar'].archivePath) but > haven't had time to try it out. > > Please let me know if you'd like to work on the Gradle stuff together, > I would be happy to collaborate :) > > Regards, > Matt > > [1] https://github.com/apache/nifi-maven > [2] https://github.com/mattyb149/nifi-gradle-nar-example > > On Tue, Jan 9, 2018 at 11:47 AM, Nicholas Deane > wrote: >> Hi, >> >> I’m working on a custom processor and want to utilize NiFi’s >> SSLContextService. >> >> In my build.gradle dependencies section, I’ve included: >> compile "org.apache.nifi:nifi-ssl-context-service-api:$nifiVersion" >> >> and in my code I’ve created the property descriptor with >> .identifiesControllerService(SSLContextService.class) >> >> When I’m configuring the processor, I noticed that the property on the >> processor says that it “Requires Controller Service: SSLContextService from >> my-custom-nar”. When I create a StandardSSLContextService from the default >> org.apache.nifi bundle, it doesn’t show up in the processor’s list (as >> expected based on that info message). >> >> I tried bringing in “nifi-ssl-context-service” and now I have two versions >> of StandardSSLContextService in the controller service list (one from the >> org.apache.nifi bundle and the other from my-custom-nar bundle). Is this how >> I should be doing something like this or is there a better way for me to use >> Controller Services across bundles and avoid having duplicates in that list? >> >> >> Notice - Confidential Information The information in this communication and >> any attachments is strictly confidential and intended only for the use of >> the individual(s) or entity(ies) named above. If you are not the intended >> recipient, any dissemination, distribution, copying or other use of the >> information contained in this communication and/or any attachment is >> strictly prohibited. If you have received this communication in error, >> please first notify the sender immediately and then delete this >> communication from all data storage devices and destroy all hard copies.
Re: [VOTE] Release Apache NiFi 1.5.0 (RC1)
+1 (binding) Release this package as nifi-1.5.0 Verified signature, hashes, build, etc. Ran through a number of scenarios with Apache NiFi Registry 0.1.0 and everything is working as expected. Thanks Joe for RMing this release! Matt On Wed, Jan 10, 2018 at 2:22 PM, Rob Moranwrote: > +1, non-binding > > * All looks good/in place following the release helper > * Reviewed help docs related to new Registry integration > * Connected a registry client and did some quick testing of basic version > control related actions > > > On Wed, Jan 10, 2018 at 1:24 PM Andrew Lim > wrote: > > > +1 (non-binding) > > > > -Ran full clean install on OS X (10.11.6) > > -Tested integration with NiFi Registry > > -Ran record reader/writer flows > > -Reviewed resolved “Core UI” component Jiras and spot checked inclusion > in > > build > > -Reviewed documentation > > > > Drew > > > > > > > On Jan 9, 2018, at 5:19 AM, Joe Witt wrote: > > > > > > Hello, > > > > > > I am pleased to be calling this vote for the source release of Apache > > > NiFi nifi-1.5.0. > > > > > > The source zip, including signatures, digests, etc. can be found at: > > > https://repository.apache.org/content/repositories/orgapachenifi-1116 > > > > > > The Git tag is nifi-1.5.0-RC1 > > > The Git commit ID is 46d30c7e92f0ad034d9b35bf1d05c350ab5547ed > > > > > https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h= > 46d30c7e92f0ad034d9b35bf1d05c350ab5547ed > > > > > > Checksums of nifi-1.5.0-source-release.zip: > > > MD5: 046f2dde4af592dd8c05e55c2bbb3c4f > > > SHA1: 63b9a68b9f89200fd31f5561956a15b45b1b9c8c > > > SHA256: 40b155c4911414907835f2eb0d5a4da798935f27f1e5134218d904fe6c94 > 2d13 > > > > > > Release artifacts are signed with the following key: > > > https://people.apache.org/keys/committer/joewitt.asc > > > > > > KEYS file available here: > > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > > > 195 issues were closed/resolved for this release: > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa? > projectId=12316020=12341668 > > > > > > Release note highlights can be found here: > > > > > https://cwiki.apache.org/confluence/display/NIFI/ > Release+Notes#ReleaseNotes-Version1.5.0 > > > > > > The vote will be open for 72 hours. > > > Please download the release candidate and evaluate the necessary items > > > including checking hashes, signatures, build > > > from source, and test. The please vote: > > > > > > [ ] +1 Release this package as nifi-1.5.0 > > > [ ] +0 no opinion > > > [ ] -1 Do not release this package because... > > > > > > -- > Rob >
Re: [VOTE] Release Apache NiFi 1.5.0 (RC1)
+1, non-binding * All looks good/in place following the release helper * Reviewed help docs related to new Registry integration * Connected a registry client and did some quick testing of basic version control related actions On Wed, Jan 10, 2018 at 1:24 PM Andrew Limwrote: > +1 (non-binding) > > -Ran full clean install on OS X (10.11.6) > -Tested integration with NiFi Registry > -Ran record reader/writer flows > -Reviewed resolved “Core UI” component Jiras and spot checked inclusion in > build > -Reviewed documentation > > Drew > > > > On Jan 9, 2018, at 5:19 AM, Joe Witt wrote: > > > > Hello, > > > > I am pleased to be calling this vote for the source release of Apache > > NiFi nifi-1.5.0. > > > > The source zip, including signatures, digests, etc. can be found at: > > https://repository.apache.org/content/repositories/orgapachenifi-1116 > > > > The Git tag is nifi-1.5.0-RC1 > > The Git commit ID is 46d30c7e92f0ad034d9b35bf1d05c350ab5547ed > > > https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=46d30c7e92f0ad034d9b35bf1d05c350ab5547ed > > > > Checksums of nifi-1.5.0-source-release.zip: > > MD5: 046f2dde4af592dd8c05e55c2bbb3c4f > > SHA1: 63b9a68b9f89200fd31f5561956a15b45b1b9c8c > > SHA256: 40b155c4911414907835f2eb0d5a4da798935f27f1e5134218d904fe6c942d13 > > > > Release artifacts are signed with the following key: > > https://people.apache.org/keys/committer/joewitt.asc > > > > KEYS file available here: > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > 195 issues were closed/resolved for this release: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12341668 > > > > Release note highlights can be found here: > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.5.0 > > > > The vote will be open for 72 hours. > > Please download the release candidate and evaluate the necessary items > > including checking hashes, signatures, build > > from source, and test. The please vote: > > > > [ ] +1 Release this package as nifi-1.5.0 > > [ ] +0 no opinion > > [ ] -1 Do not release this package because... > > -- Rob
Re: [VOTE] Release Apache NiFi 1.5.0 (RC1)
+1 (non-binding) -Ran full clean install on OS X (10.11.6) -Tested integration with NiFi Registry -Ran record reader/writer flows -Reviewed resolved “Core UI” component Jiras and spot checked inclusion in build -Reviewed documentation Drew > On Jan 9, 2018, at 5:19 AM, Joe Wittwrote: > > Hello, > > I am pleased to be calling this vote for the source release of Apache > NiFi nifi-1.5.0. > > The source zip, including signatures, digests, etc. can be found at: > https://repository.apache.org/content/repositories/orgapachenifi-1116 > > The Git tag is nifi-1.5.0-RC1 > The Git commit ID is 46d30c7e92f0ad034d9b35bf1d05c350ab5547ed > https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=46d30c7e92f0ad034d9b35bf1d05c350ab5547ed > > Checksums of nifi-1.5.0-source-release.zip: > MD5: 046f2dde4af592dd8c05e55c2bbb3c4f > SHA1: 63b9a68b9f89200fd31f5561956a15b45b1b9c8c > SHA256: 40b155c4911414907835f2eb0d5a4da798935f27f1e5134218d904fe6c942d13 > > Release artifacts are signed with the following key: > https://people.apache.org/keys/committer/joewitt.asc > > KEYS file available here: > https://dist.apache.org/repos/dist/release/nifi/KEYS > > 195 issues were closed/resolved for this release: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12341668 > > Release note highlights can be found here: > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.5.0 > > The vote will be open for 72 hours. > Please download the release candidate and evaluate the necessary items > including checking hashes, signatures, build > from source, and test. The please vote: > > [ ] +1 Release this package as nifi-1.5.0 > [ ] +0 no opinion > [ ] -1 Do not release this package because...
Re: [VOTE] Release Apache NiFi 1.5.0 (RC1)
+1 - Verified checksums, signature and commit ID - Ran build w/ contrib-check with OpenJDK 1.8.0_131 on Amazon Linux 2017.03 - Tested version control and flow registry, CountText, FlattenJson and some other flows - Tested RPM build and install on Amazon Linux 2017.03 - Skimmed L - Gave it lots of <3 -joey On Jan 10, 2018, 9:14 AM -0700, Chris Herrera, wrote: > +1 (non-binding) > > Built with contrib-check > Verified keys and hashes > > Ran through several flows in an oidc secured environment including several > custom processors. All seems working. > > Looks like a great release. Thanks guys! > > Regards, > Chris > > On Jan 10, 2018, 9:37 AM -0600, Jeff Zemerick , wrote: > > +1 non-binding > > > > Built with contrib-check. > > Stepped through release guide. > > > > Ran into a minor issue with the TestListenSMTP unit tests on OSX but it > > might be pretty specific to my computer. > > > > https://issues.apache.org/jira/browse/NIFI-4760 > > > > > > On Wed, Jan 10, 2018 at 10:26 AM, Pierre Villard < > > pierre.villard...@gmail.com> wrote: > > > > > +1 (binding) > > > > > > Went through release helper guide and all looks good to me. > > > Tested integration with a running registry instance. > > > Ran some test workflows in a secured env and tested recent fixed about > > > authorizers. > > > > > > Thanks for taking care of the release Joe! > > > Great job from all the community around this release! Integration with the > > > registry is neat. > > > > > > Pierre > > > > > > > > > > > > 2018-01-10 16:16 GMT+01:00 Bryan Bende : > > > > > > > +1 (binding) > > > > > > > > - Ran through release helper with no issues > > > > - Ran into a minor issue related to component versioning when using > > > > the registry and created this JIRA [1], would be more of an issue for > > > > next release > > > > > > > > [1] https://issues.apache.org/jira/browse/NIFI-4763 > > > > > > > > > > > > On Wed, Jan 10, 2018 at 10:05 AM, Matt Burgess > > > wrote: > > > > > +1 (binding), ran through release guide with no issues (verified sigs > > > > > & sums), ran various flows using record processors, the new Jackson > > > > > CSV parser, provenance reporting task with new filtering capability > > > > > and output fields, etc. > > > > > > > > > > On Tue, Jan 9, 2018 at 5:19 AM, Joe Witt wrote: > > > > > > Hello, > > > > > > > > > > > > I am pleased to be calling this vote for the source release of > > > > > > Apache > > > > > > NiFi nifi-1.5.0. > > > > > > > > > > > > The source zip, including signatures, digests, etc. can be found at: > > > > > > https://repository.apache.org/content/repositories/orgapachenifi-1116 > > > > > > > > > > > > The Git tag is nifi-1.5.0-RC1 > > > > > > The Git commit ID is 46d30c7e92f0ad034d9b35bf1d05c350ab5547ed > > > > > > https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h= > > > > 46d30c7e92f0ad034d9b35bf1d05c350ab5547ed > > > > > > > > > > > > Checksums of nifi-1.5.0-source-release.zip: > > > > > > MD5: 046f2dde4af592dd8c05e55c2bbb3c4f > > > > > > SHA1: 63b9a68b9f89200fd31f5561956a15b45b1b9c8c > > > > > > SHA256: 40b155c4911414907835f2eb0d5a4da798935f27f1e5134218d904fe6c94 > > > > 2d13 > > > > > > > > > > > > Release artifacts are signed with the following key: > > > > > > https://people.apache.org/keys/committer/joewitt.asc > > > > > > > > > > > > KEYS file available here: > > > > > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > > > > > > > > > 195 issues were closed/resolved for this release: > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa? > > > > projectId=12316020=12341668 > > > > > > > > > > > > Release note highlights can be found here: > > > > > > https://cwiki.apache.org/confluence/display/NIFI/ > > > > Release+Notes#ReleaseNotes-Version1.5.0 > > > > > > > > > > > > The vote will be open for 72 hours. > > > > > > Please download the release candidate and evaluate the necessary > > > > > > items > > > > > > including checking hashes, signatures, build > > > > > > from source, and test. The please vote: > > > > > > > > > > > > [ ] +1 Release this package as nifi-1.5.0 > > > > > > [ ] +0 no opinion > > > > > > [ ] -1 Do not release this package because... > > > > > > >
Re: [VOTE] Release Apache NiFi 1.5.0 (RC1)
+1 (binding) Ran through release helper with no issues Started NiFi and configured a NiFi Registry Client Performed SDLC functionalities on PG's On Wed, Jan 10, 2018 at 11:13 AM, Chris Herrerawrote: > +1 (non-binding) > > Built with contrib-check > Verified keys and hashes > > Ran through several flows in an oidc secured environment including several > custom processors. All seems working. > > Looks like a great release. Thanks guys! > > Regards, > Chris > > On Jan 10, 2018, 9:37 AM -0600, Jeff Zemerick , > wrote: > > +1 non-binding > > > > Built with contrib-check. > > Stepped through release guide. > > > > Ran into a minor issue with the TestListenSMTP unit tests on OSX but it > > might be pretty specific to my computer. > > > > https://issues.apache.org/jira/browse/NIFI-4760 > > > > > > On Wed, Jan 10, 2018 at 10:26 AM, Pierre Villard < > > pierre.villard...@gmail.com> wrote: > > > > > +1 (binding) > > > > > > Went through release helper guide and all looks good to me. > > > Tested integration with a running registry instance. > > > Ran some test workflows in a secured env and tested recent fixed about > > > authorizers. > > > > > > Thanks for taking care of the release Joe! > > > Great job from all the community around this release! Integration with > the > > > registry is neat. > > > > > > Pierre > > > > > > > > > > > > 2018-01-10 16:16 GMT+01:00 Bryan Bende : > > > > > > > +1 (binding) > > > > > > > > - Ran through release helper with no issues > > > > - Ran into a minor issue related to component versioning when using > > > > the registry and created this JIRA [1], would be more of an issue for > > > > next release > > > > > > > > [1] https://issues.apache.org/jira/browse/NIFI-4763 > > > > > > > > > > > > On Wed, Jan 10, 2018 at 10:05 AM, Matt Burgess > > > wrote: > > > > > +1 (binding), ran through release guide with no issues (verified > sigs > > > > > & sums), ran various flows using record processors, the new Jackson > > > > > CSV parser, provenance reporting task with new filtering capability > > > > > and output fields, etc. > > > > > > > > > > On Tue, Jan 9, 2018 at 5:19 AM, Joe Witt > wrote: > > > > > > Hello, > > > > > > > > > > > > I am pleased to be calling this vote for the source release of > Apache > > > > > > NiFi nifi-1.5.0. > > > > > > > > > > > > The source zip, including signatures, digests, etc. can be found > at: > > > > > > https://repository.apache.org/content/repositories/ > orgapachenifi-1116 > > > > > > > > > > > > The Git tag is nifi-1.5.0-RC1 > > > > > > The Git commit ID is 46d30c7e92f0ad034d9b35bf1d05c350ab5547ed > > > > > > https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h= > > > > 46d30c7e92f0ad034d9b35bf1d05c350ab5547ed > > > > > > > > > > > > Checksums of nifi-1.5.0-source-release.zip: > > > > > > MD5: 046f2dde4af592dd8c05e55c2bbb3c4f > > > > > > SHA1: 63b9a68b9f89200fd31f5561956a15b45b1b9c8c > > > > > > SHA256: 40b155c4911414907835f2eb0d5a4d > a798935f27f1e5134218d904fe6c94 > > > > 2d13 > > > > > > > > > > > > Release artifacts are signed with the following key: > > > > > > https://people.apache.org/keys/committer/joewitt.asc > > > > > > > > > > > > KEYS file available here: > > > > > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > > > > > > > > > 195 issues were closed/resolved for this release: > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa? > > > > projectId=12316020=12341668 > > > > > > > > > > > > Release note highlights can be found here: > > > > > > https://cwiki.apache.org/confluence/display/NIFI/ > > > > Release+Notes#ReleaseNotes-Version1.5.0 > > > > > > > > > > > > The vote will be open for 72 hours. > > > > > > Please download the release candidate and evaluate the necessary > items > > > > > > including checking hashes, signatures, build > > > > > > from source, and test. The please vote: > > > > > > > > > > > > [ ] +1 Release this package as nifi-1.5.0 > > > > > > [ ] +0 no opinion > > > > > > [ ] -1 Do not release this package because... > > > > > > > >
Re: NiFI 1.4.0 UI can't be displayed in an IFrame?
Virgil, Understood. I would encourage you to open a ticket documenting this need as there may be other users who also need it, and a native feature will be more useful than requiring people to manually change code and build the application with every release. Thanks. Andy LoPresto alopre...@apache.org alopresto.apa...@gmail.com PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > On Jan 10, 2018, at 7:20 AM, tanezavmwrote: > > Hi Andy, > > Thanks for the very helpful explanation. I believe I would go to option 5 to > change the value provided to the response header. We have some kind of > enterprise portal and have a legitimate need to display a NiFi UI within a > frame. > > Regards, > Virgil > > > > -- > Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/ signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [VOTE] Release Apache NiFi 1.5.0 (RC1)
+1 (non-binding) Built with contrib-check Verified keys and hashes Ran through several flows in an oidc secured environment including several custom processors. All seems working. Looks like a great release. Thanks guys! Regards, Chris On Jan 10, 2018, 9:37 AM -0600, Jeff Zemerick, wrote: > +1 non-binding > > Built with contrib-check. > Stepped through release guide. > > Ran into a minor issue with the TestListenSMTP unit tests on OSX but it > might be pretty specific to my computer. > > https://issues.apache.org/jira/browse/NIFI-4760 > > > On Wed, Jan 10, 2018 at 10:26 AM, Pierre Villard < > pierre.villard...@gmail.com> wrote: > > > +1 (binding) > > > > Went through release helper guide and all looks good to me. > > Tested integration with a running registry instance. > > Ran some test workflows in a secured env and tested recent fixed about > > authorizers. > > > > Thanks for taking care of the release Joe! > > Great job from all the community around this release! Integration with the > > registry is neat. > > > > Pierre > > > > > > > > 2018-01-10 16:16 GMT+01:00 Bryan Bende : > > > > > +1 (binding) > > > > > > - Ran through release helper with no issues > > > - Ran into a minor issue related to component versioning when using > > > the registry and created this JIRA [1], would be more of an issue for > > > next release > > > > > > [1] https://issues.apache.org/jira/browse/NIFI-4763 > > > > > > > > > On Wed, Jan 10, 2018 at 10:05 AM, Matt Burgess > > wrote: > > > > +1 (binding), ran through release guide with no issues (verified sigs > > > > & sums), ran various flows using record processors, the new Jackson > > > > CSV parser, provenance reporting task with new filtering capability > > > > and output fields, etc. > > > > > > > > On Tue, Jan 9, 2018 at 5:19 AM, Joe Witt wrote: > > > > > Hello, > > > > > > > > > > I am pleased to be calling this vote for the source release of Apache > > > > > NiFi nifi-1.5.0. > > > > > > > > > > The source zip, including signatures, digests, etc. can be found at: > > > > > https://repository.apache.org/content/repositories/orgapachenifi-1116 > > > > > > > > > > The Git tag is nifi-1.5.0-RC1 > > > > > The Git commit ID is 46d30c7e92f0ad034d9b35bf1d05c350ab5547ed > > > > > https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h= > > > 46d30c7e92f0ad034d9b35bf1d05c350ab5547ed > > > > > > > > > > Checksums of nifi-1.5.0-source-release.zip: > > > > > MD5: 046f2dde4af592dd8c05e55c2bbb3c4f > > > > > SHA1: 63b9a68b9f89200fd31f5561956a15b45b1b9c8c > > > > > SHA256: 40b155c4911414907835f2eb0d5a4da798935f27f1e5134218d904fe6c94 > > > 2d13 > > > > > > > > > > Release artifacts are signed with the following key: > > > > > https://people.apache.org/keys/committer/joewitt.asc > > > > > > > > > > KEYS file available here: > > > > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > > > > > > > 195 issues were closed/resolved for this release: > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa? > > > projectId=12316020=12341668 > > > > > > > > > > Release note highlights can be found here: > > > > > https://cwiki.apache.org/confluence/display/NIFI/ > > > Release+Notes#ReleaseNotes-Version1.5.0 > > > > > > > > > > The vote will be open for 72 hours. > > > > > Please download the release candidate and evaluate the necessary items > > > > > including checking hashes, signatures, build > > > > > from source, and test. The please vote: > > > > > > > > > > [ ] +1 Release this package as nifi-1.5.0 > > > > > [ ] +0 no opinion > > > > > [ ] -1 Do not release this package because... > > > > >
Re: [VOTE] Release Apache NiFi 1.5.0 (RC1)
+1 non-binding Built with contrib-check. Stepped through release guide. Ran into a minor issue with the TestListenSMTP unit tests on OSX but it might be pretty specific to my computer. https://issues.apache.org/jira/browse/NIFI-4760 On Wed, Jan 10, 2018 at 10:26 AM, Pierre Villard < pierre.villard...@gmail.com> wrote: > +1 (binding) > > Went through release helper guide and all looks good to me. > Tested integration with a running registry instance. > Ran some test workflows in a secured env and tested recent fixed about > authorizers. > > Thanks for taking care of the release Joe! > Great job from all the community around this release! Integration with the > registry is neat. > > Pierre > > > > 2018-01-10 16:16 GMT+01:00 Bryan Bende: > > > +1 (binding) > > > > - Ran through release helper with no issues > > - Ran into a minor issue related to component versioning when using > > the registry and created this JIRA [1], would be more of an issue for > > next release > > > > [1] https://issues.apache.org/jira/browse/NIFI-4763 > > > > > > On Wed, Jan 10, 2018 at 10:05 AM, Matt Burgess > > wrote: > > > +1 (binding), ran through release guide with no issues (verified sigs > > > & sums), ran various flows using record processors, the new Jackson > > > CSV parser, provenance reporting task with new filtering capability > > > and output fields, etc. > > > > > > On Tue, Jan 9, 2018 at 5:19 AM, Joe Witt wrote: > > >> Hello, > > >> > > >> I am pleased to be calling this vote for the source release of Apache > > >> NiFi nifi-1.5.0. > > >> > > >> The source zip, including signatures, digests, etc. can be found at: > > >> https://repository.apache.org/content/repositories/orgapachenifi-1116 > > >> > > >> The Git tag is nifi-1.5.0-RC1 > > >> The Git commit ID is 46d30c7e92f0ad034d9b35bf1d05c350ab5547ed > > >> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h= > > 46d30c7e92f0ad034d9b35bf1d05c350ab5547ed > > >> > > >> Checksums of nifi-1.5.0-source-release.zip: > > >> MD5: 046f2dde4af592dd8c05e55c2bbb3c4f > > >> SHA1: 63b9a68b9f89200fd31f5561956a15b45b1b9c8c > > >> SHA256: 40b155c4911414907835f2eb0d5a4da798935f27f1e5134218d904fe6c94 > > 2d13 > > >> > > >> Release artifacts are signed with the following key: > > >> https://people.apache.org/keys/committer/joewitt.asc > > >> > > >> KEYS file available here: > > >> https://dist.apache.org/repos/dist/release/nifi/KEYS > > >> > > >> 195 issues were closed/resolved for this release: > > >> https://issues.apache.org/jira/secure/ReleaseNote.jspa? > > projectId=12316020=12341668 > > >> > > >> Release note highlights can be found here: > > >> https://cwiki.apache.org/confluence/display/NIFI/ > > Release+Notes#ReleaseNotes-Version1.5.0 > > >> > > >> The vote will be open for 72 hours. > > >> Please download the release candidate and evaluate the necessary items > > >> including checking hashes, signatures, build > > >> from source, and test. The please vote: > > >> > > >> [ ] +1 Release this package as nifi-1.5.0 > > >> [ ] +0 no opinion > > >> [ ] -1 Do not release this package because... > > >
Re: NiFI 1.4.0 UI can't be displayed in an IFrame?
Hi Andy, Thanks for the very helpful explanation. I believe I would go to option 5 to change the value provided to the response header. We have some kind of enterprise portal and have a legitimate need to display a NiFi UI within a frame. Regards, Virgil -- Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/
Re: [VOTE] Release Apache NiFi 1.5.0 (RC1)
+1 (binding) Went through release helper guide and all looks good to me. Tested integration with a running registry instance. Ran some test workflows in a secured env and tested recent fixed about authorizers. Thanks for taking care of the release Joe! Great job from all the community around this release! Integration with the registry is neat. Pierre 2018-01-10 16:16 GMT+01:00 Bryan Bende: > +1 (binding) > > - Ran through release helper with no issues > - Ran into a minor issue related to component versioning when using > the registry and created this JIRA [1], would be more of an issue for > next release > > [1] https://issues.apache.org/jira/browse/NIFI-4763 > > > On Wed, Jan 10, 2018 at 10:05 AM, Matt Burgess > wrote: > > +1 (binding), ran through release guide with no issues (verified sigs > > & sums), ran various flows using record processors, the new Jackson > > CSV parser, provenance reporting task with new filtering capability > > and output fields, etc. > > > > On Tue, Jan 9, 2018 at 5:19 AM, Joe Witt wrote: > >> Hello, > >> > >> I am pleased to be calling this vote for the source release of Apache > >> NiFi nifi-1.5.0. > >> > >> The source zip, including signatures, digests, etc. can be found at: > >> https://repository.apache.org/content/repositories/orgapachenifi-1116 > >> > >> The Git tag is nifi-1.5.0-RC1 > >> The Git commit ID is 46d30c7e92f0ad034d9b35bf1d05c350ab5547ed > >> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h= > 46d30c7e92f0ad034d9b35bf1d05c350ab5547ed > >> > >> Checksums of nifi-1.5.0-source-release.zip: > >> MD5: 046f2dde4af592dd8c05e55c2bbb3c4f > >> SHA1: 63b9a68b9f89200fd31f5561956a15b45b1b9c8c > >> SHA256: 40b155c4911414907835f2eb0d5a4da798935f27f1e5134218d904fe6c94 > 2d13 > >> > >> Release artifacts are signed with the following key: > >> https://people.apache.org/keys/committer/joewitt.asc > >> > >> KEYS file available here: > >> https://dist.apache.org/repos/dist/release/nifi/KEYS > >> > >> 195 issues were closed/resolved for this release: > >> https://issues.apache.org/jira/secure/ReleaseNote.jspa? > projectId=12316020=12341668 > >> > >> Release note highlights can be found here: > >> https://cwiki.apache.org/confluence/display/NIFI/ > Release+Notes#ReleaseNotes-Version1.5.0 > >> > >> The vote will be open for 72 hours. > >> Please download the release candidate and evaluate the necessary items > >> including checking hashes, signatures, build > >> from source, and test. The please vote: > >> > >> [ ] +1 Release this package as nifi-1.5.0 > >> [ ] +0 no opinion > >> [ ] -1 Do not release this package because... >
Re: [VOTE] Release Apache NiFi 1.5.0 (RC1)
+1 (binding) - Ran through release helper with no issues - Ran into a minor issue related to component versioning when using the registry and created this JIRA [1], would be more of an issue for next release [1] https://issues.apache.org/jira/browse/NIFI-4763 On Wed, Jan 10, 2018 at 10:05 AM, Matt Burgesswrote: > +1 (binding), ran through release guide with no issues (verified sigs > & sums), ran various flows using record processors, the new Jackson > CSV parser, provenance reporting task with new filtering capability > and output fields, etc. > > On Tue, Jan 9, 2018 at 5:19 AM, Joe Witt wrote: >> Hello, >> >> I am pleased to be calling this vote for the source release of Apache >> NiFi nifi-1.5.0. >> >> The source zip, including signatures, digests, etc. can be found at: >> https://repository.apache.org/content/repositories/orgapachenifi-1116 >> >> The Git tag is nifi-1.5.0-RC1 >> The Git commit ID is 46d30c7e92f0ad034d9b35bf1d05c350ab5547ed >> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=46d30c7e92f0ad034d9b35bf1d05c350ab5547ed >> >> Checksums of nifi-1.5.0-source-release.zip: >> MD5: 046f2dde4af592dd8c05e55c2bbb3c4f >> SHA1: 63b9a68b9f89200fd31f5561956a15b45b1b9c8c >> SHA256: 40b155c4911414907835f2eb0d5a4da798935f27f1e5134218d904fe6c942d13 >> >> Release artifacts are signed with the following key: >> https://people.apache.org/keys/committer/joewitt.asc >> >> KEYS file available here: >> https://dist.apache.org/repos/dist/release/nifi/KEYS >> >> 195 issues were closed/resolved for this release: >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12341668 >> >> Release note highlights can be found here: >> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.5.0 >> >> The vote will be open for 72 hours. >> Please download the release candidate and evaluate the necessary items >> including checking hashes, signatures, build >> from source, and test. The please vote: >> >> [ ] +1 Release this package as nifi-1.5.0 >> [ ] +0 no opinion >> [ ] -1 Do not release this package because...
Re: [VOTE] Release Apache NiFi 1.5.0 (RC1)
FYI, a user found a serious bug in PutMongo with updates/upserts. I'll try to get a PR done today, tomorrow at the latest. On Wed, Jan 10, 2018 at 6:41 AM, Marcwrote: > +1, binding. > >* Verified sigs/hashes >* Used release guide with no issues >* Ran through some tests with flow versioning functionality. >* Ran usual test flows > > > > On Wed, Jan 10, 2018 at 6:38 AM, Marco Gaido > wrote: > > > +1 (not binding). Ran through release guide with no issues and run some > > workflows. > > > > 2018-01-10 4:41 GMT+01:00 Jeremy Dyer : > > > > > +1 non binding. Ran through release guide with no issues and ran > several > > > test workflows from personal projects > > > > > > - Jeremy Dyer > > > > > > > On Jan 9, 2018, at 8:11 PM, Andy LoPresto > > wrote: > > > > > > > > +1, binding > > > > > > > > I performed the following verifications: > > > > > > > > * verified the GPG key signature > > > > * verified the MD5/SHA1/SHA256 checksums > > > > * verified the git commit ID > > > > * verified the presence of LICENSE, NOTICE, and README > > > > * verified the Maven build was successful, including all unit tests, > > RAT > > > check, and code style guidelines > > > > * verified the application started successfully > > > > * verified the new behavior for host header handling was present > > > > * verified the application integrates successfully with the Apache > NiFi > > > Registry > > > > * verified the CountText processor works as anticipated > > > > * verified the flow versioning functionality by making local changes, > > > committing, and restoring prior versions of the flow > > > > > > > > Andy LoPresto > > > > alopre...@apache.org > > > > alopresto.apa...@gmail.com > > > > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > > > > > > > >> On Jan 9, 2018, at 9:13 AM, Mark Payne > wrote: > > > >> > > > >> +1 (binding) - Release this package as nifi-1.5.0 > > > >> > > > >> Was able to successfully build with contrib-check and grpc profile. > > > Verified MD5 sum. > > > >> Started up, added a Flow Registry Client pointing to an existing > Flow > > > Registry and was > > > >> able to immediately import a flow and start it running. This flow > also > > > verified the fix for > > > >> NIFI-4749 made it into the build yesterday. > > > >> > > > >> Thanks for taking on the RM duties this time, Joe! And a big thank > you > > > and congrats > > > >> to all of the members of the community that contributed to this > > release > > > - code, JIRA's, > > > >> docs, and support! > > > >> > > > >> Thanks > > > >> -Mark > > > >> > > > >> > > > >>> On Jan 9, 2018, at 5:19 AM, Joe Witt wrote: > > > >>> > > > >>> Hello, > > > >>> > > > >>> I am pleased to be calling this vote for the source release of > Apache > > > >>> NiFi nifi-1.5.0. > > > >>> > > > >>> The source zip, including signatures, digests, etc. can be found > at: > > > >>> https://repository.apache.org/content/repositories/ > > orgapachenifi-1116 > > > >>> > > > >>> The Git tag is nifi-1.5.0-RC1 > > > >>> The Git commit ID is 46d30c7e92f0ad034d9b35bf1d05c350ab5547ed > > > >>> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h= > > > 46d30c7e92f0ad034d9b35bf1d05c350ab5547ed > > > >>> > > > >>> Checksums of nifi-1.5.0-source-release.zip: > > > >>> MD5: 046f2dde4af592dd8c05e55c2bbb3c4f > > > >>> SHA1: 63b9a68b9f89200fd31f5561956a15b45b1b9c8c > > > >>> SHA256: 40b155c4911414907835f2eb0d5a4d > a798935f27f1e5134218d904fe6c94 > > > 2d13 > > > >>> > > > >>> Release artifacts are signed with the following key: > > > >>> https://people.apache.org/keys/committer/joewitt.asc > > > >>> > > > >>> KEYS file available here: > > > >>> https://dist.apache.org/repos/dist/release/nifi/KEYS > > > >>> > > > >>> 195 issues were closed/resolved for this release: > > > >>> https://issues.apache.org/jira/secure/ReleaseNote.jspa? > > > projectId=12316020=12341668 > > > >>> > > > >>> Release note highlights can be found here: > > > >>> https://cwiki.apache.org/confluence/display/NIFI/ > > > Release+Notes#ReleaseNotes-Version1.5.0 > > > >>> > > > >>> The vote will be open for 72 hours. > > > >>> Please download the release candidate and evaluate the necessary > > items > > > >>> including checking hashes, signatures, build > > > >>> from source, and test. The please vote: > > > >>> > > > >>> [ ] +1 Release this package as nifi-1.5.0 > > > >>> [ ] +0 no opinion > > > >>> [ ] -1 Do not release this package because... > > > >> > > > > > > > > > >
Re: [VOTE] Release Apache NiFi 1.5.0 (RC1)
+1, binding. * Verified sigs/hashes * Used release guide with no issues * Ran through some tests with flow versioning functionality. * Ran usual test flows On Wed, Jan 10, 2018 at 6:38 AM, Marco Gaidowrote: > +1 (not binding). Ran through release guide with no issues and run some > workflows. > > 2018-01-10 4:41 GMT+01:00 Jeremy Dyer : > > > +1 non binding. Ran through release guide with no issues and ran several > > test workflows from personal projects > > > > - Jeremy Dyer > > > > > On Jan 9, 2018, at 8:11 PM, Andy LoPresto > wrote: > > > > > > +1, binding > > > > > > I performed the following verifications: > > > > > > * verified the GPG key signature > > > * verified the MD5/SHA1/SHA256 checksums > > > * verified the git commit ID > > > * verified the presence of LICENSE, NOTICE, and README > > > * verified the Maven build was successful, including all unit tests, > RAT > > check, and code style guidelines > > > * verified the application started successfully > > > * verified the new behavior for host header handling was present > > > * verified the application integrates successfully with the Apache NiFi > > Registry > > > * verified the CountText processor works as anticipated > > > * verified the flow versioning functionality by making local changes, > > committing, and restoring prior versions of the flow > > > > > > Andy LoPresto > > > alopre...@apache.org > > > alopresto.apa...@gmail.com > > > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > > > > > >> On Jan 9, 2018, at 9:13 AM, Mark Payne wrote: > > >> > > >> +1 (binding) - Release this package as nifi-1.5.0 > > >> > > >> Was able to successfully build with contrib-check and grpc profile. > > Verified MD5 sum. > > >> Started up, added a Flow Registry Client pointing to an existing Flow > > Registry and was > > >> able to immediately import a flow and start it running. This flow also > > verified the fix for > > >> NIFI-4749 made it into the build yesterday. > > >> > > >> Thanks for taking on the RM duties this time, Joe! And a big thank you > > and congrats > > >> to all of the members of the community that contributed to this > release > > - code, JIRA's, > > >> docs, and support! > > >> > > >> Thanks > > >> -Mark > > >> > > >> > > >>> On Jan 9, 2018, at 5:19 AM, Joe Witt wrote: > > >>> > > >>> Hello, > > >>> > > >>> I am pleased to be calling this vote for the source release of Apache > > >>> NiFi nifi-1.5.0. > > >>> > > >>> The source zip, including signatures, digests, etc. can be found at: > > >>> https://repository.apache.org/content/repositories/ > orgapachenifi-1116 > > >>> > > >>> The Git tag is nifi-1.5.0-RC1 > > >>> The Git commit ID is 46d30c7e92f0ad034d9b35bf1d05c350ab5547ed > > >>> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h= > > 46d30c7e92f0ad034d9b35bf1d05c350ab5547ed > > >>> > > >>> Checksums of nifi-1.5.0-source-release.zip: > > >>> MD5: 046f2dde4af592dd8c05e55c2bbb3c4f > > >>> SHA1: 63b9a68b9f89200fd31f5561956a15b45b1b9c8c > > >>> SHA256: 40b155c4911414907835f2eb0d5a4da798935f27f1e5134218d904fe6c94 > > 2d13 > > >>> > > >>> Release artifacts are signed with the following key: > > >>> https://people.apache.org/keys/committer/joewitt.asc > > >>> > > >>> KEYS file available here: > > >>> https://dist.apache.org/repos/dist/release/nifi/KEYS > > >>> > > >>> 195 issues were closed/resolved for this release: > > >>> https://issues.apache.org/jira/secure/ReleaseNote.jspa? > > projectId=12316020=12341668 > > >>> > > >>> Release note highlights can be found here: > > >>> https://cwiki.apache.org/confluence/display/NIFI/ > > Release+Notes#ReleaseNotes-Version1.5.0 > > >>> > > >>> The vote will be open for 72 hours. > > >>> Please download the release candidate and evaluate the necessary > items > > >>> including checking hashes, signatures, build > > >>> from source, and test. The please vote: > > >>> > > >>> [ ] +1 Release this package as nifi-1.5.0 > > >>> [ ] +0 no opinion > > >>> [ ] -1 Do not release this package because... > > >> > > > > > >
Re: [VOTE] Release Apache NiFi 1.5.0 (RC1)
+1 (not binding). Ran through release guide with no issues and run some workflows. 2018-01-10 4:41 GMT+01:00 Jeremy Dyer: > +1 non binding. Ran through release guide with no issues and ran several > test workflows from personal projects > > - Jeremy Dyer > > > On Jan 9, 2018, at 8:11 PM, Andy LoPresto wrote: > > > > +1, binding > > > > I performed the following verifications: > > > > * verified the GPG key signature > > * verified the MD5/SHA1/SHA256 checksums > > * verified the git commit ID > > * verified the presence of LICENSE, NOTICE, and README > > * verified the Maven build was successful, including all unit tests, RAT > check, and code style guidelines > > * verified the application started successfully > > * verified the new behavior for host header handling was present > > * verified the application integrates successfully with the Apache NiFi > Registry > > * verified the CountText processor works as anticipated > > * verified the flow versioning functionality by making local changes, > committing, and restoring prior versions of the flow > > > > Andy LoPresto > > alopre...@apache.org > > alopresto.apa...@gmail.com > > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > > > >> On Jan 9, 2018, at 9:13 AM, Mark Payne wrote: > >> > >> +1 (binding) - Release this package as nifi-1.5.0 > >> > >> Was able to successfully build with contrib-check and grpc profile. > Verified MD5 sum. > >> Started up, added a Flow Registry Client pointing to an existing Flow > Registry and was > >> able to immediately import a flow and start it running. This flow also > verified the fix for > >> NIFI-4749 made it into the build yesterday. > >> > >> Thanks for taking on the RM duties this time, Joe! And a big thank you > and congrats > >> to all of the members of the community that contributed to this release > - code, JIRA's, > >> docs, and support! > >> > >> Thanks > >> -Mark > >> > >> > >>> On Jan 9, 2018, at 5:19 AM, Joe Witt wrote: > >>> > >>> Hello, > >>> > >>> I am pleased to be calling this vote for the source release of Apache > >>> NiFi nifi-1.5.0. > >>> > >>> The source zip, including signatures, digests, etc. can be found at: > >>> https://repository.apache.org/content/repositories/orgapachenifi-1116 > >>> > >>> The Git tag is nifi-1.5.0-RC1 > >>> The Git commit ID is 46d30c7e92f0ad034d9b35bf1d05c350ab5547ed > >>> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h= > 46d30c7e92f0ad034d9b35bf1d05c350ab5547ed > >>> > >>> Checksums of nifi-1.5.0-source-release.zip: > >>> MD5: 046f2dde4af592dd8c05e55c2bbb3c4f > >>> SHA1: 63b9a68b9f89200fd31f5561956a15b45b1b9c8c > >>> SHA256: 40b155c4911414907835f2eb0d5a4da798935f27f1e5134218d904fe6c94 > 2d13 > >>> > >>> Release artifacts are signed with the following key: > >>> https://people.apache.org/keys/committer/joewitt.asc > >>> > >>> KEYS file available here: > >>> https://dist.apache.org/repos/dist/release/nifi/KEYS > >>> > >>> 195 issues were closed/resolved for this release: > >>> https://issues.apache.org/jira/secure/ReleaseNote.jspa? > projectId=12316020=12341668 > >>> > >>> Release note highlights can be found here: > >>> https://cwiki.apache.org/confluence/display/NIFI/ > Release+Notes#ReleaseNotes-Version1.5.0 > >>> > >>> The vote will be open for 72 hours. > >>> Please download the release candidate and evaluate the necessary items > >>> including checking hashes, signatures, build > >>> from source, and test. The please vote: > >>> > >>> [ ] +1 Release this package as nifi-1.5.0 > >>> [ ] +0 no opinion > >>> [ ] -1 Do not release this package because... > >> > > >
Re: PutMongo 1.3.0 - Upsert issue
Dear Pierre, First all many thnaks for your help, we were able to use the copy you provided us and restart Nifi with 1.5.0 module. But it's appear that don't realy work like expected. If we try to update some attributes with the $set commant it don't work. *Original MongoDb record :* { "_id" : ObjectId("5a535bcea33116f026ef65f0"), "type" : "Cc", "nmess" : 3172, "idgtr" : "C-0--00061--0-CMF-RMF", "zone" : 1.0, "idzone" : "NULL", "cmf" : 24, "rmf" : 24, "carrefour" : 61, "idcarrefour" : 2, "last_update" : "2018-01-09T13:49:58", "libelle" : " Henrique#Cebolas", "geojson" : "{\"features\":[{\"geometry\":{\"coordinates\":[\"-9.132289080874671\",\"38.708011\"],\"type\":\"Point\"},\"type\":\"Feature\"}],\"type\":\"FeatureCollection\"}", "positionOk" : true, "orientation" : 0 } *Update request throw putmongo processor :* { "$set": { "type":"Cc", "nmess":14488, "idgtr":"C-0--00088--0-CMF-RMF", "last_update":"2018-01-10T09:32:35", "libelle":"Bonifacio_Estefan. " } } -- Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/