Re: Nifi 2.0.0 Major release timeline
My 2 cents: I think AWS SDK 1.x should be removed from NiFi 2.0 before the GA release. I have started working on removing AWS SDK 1.x and I hope to share a PR soon. Sean On Thu, Jul 4, 2024 at 1:04 PM Joe Witt wrote: > Ajay > > We do not have a specific date in mind. I believe largely we've completed > the major efforts we had intended for 2.0 and that even went further to > include a completely re-written UI which is a huge help. We do continue to > find unmaintained or security relevant code with limited maintenance and > we're aggressively cleaning all that up. We need to ensure we've cleaned > up all deprecated bits and are putting ourselves in the best position to > maintain, secure, and add capability as we go. > > Not speaking for the community but my personal take is we're likely 1-2 > months away now from minting a release as GA of 2.0 as what I see that > remains is pretty purely just code removal/clean-up. There are always one > or two surprises that emerge but the 2.0 line is looking really good and is > already considerably in use for production purposes so stability is there. > > Thanks > Joe > > On Thu, Jul 4, 2024 at 6:16 AM Premarajan, Ajay > wrote: > > > Hi Team, > > > > We are currently using NiFi version 1.26 in our production environment. > Is > > there a scheduled timeline for the major release of NiFi 2.0.0, or an > > estimate of how many milestone releases are planned before the major > > version is released? > > > > > > Mit freundlichen Grüßen / Kind regards > > > > Ajay Premarajan > > > > >
Re: Regarding issues facing on NIFI Remote process group
Hi NIFI Team, I hope this email finds you well. I am sending this email to kindly remind you about the mail sent on last Monday [01-07-2024]. I would greatly appreciate it if you take a moment to review my previous mail and provide your feedback or response. Please let me know if there is anything else I can assist you with. I value your input and look forward to hearing from you soon. Thanks & Regards, Dharani T. From: Tirumanyam, Dharani Date: Tuesday, 2 July 2024 at 8:16 AM To: dev@nifi.apache.org Cc: Pulimi, Satish , Shankarprasad, Raghuveera Subject: Re: Regarding issues facing on NIFI Remote process group Sorry for the spam, Please find the attachments here Thanks & Regards, Dharani Tirumanyam. From: Tirumanyam, Dharani Date: Monday, 1 July 2024 at 9:42 PM To: dev@nifi.apache.org Cc: Pulimi, Satish , Shankarprasad, Raghuveera , Tirumanyam, Dharani Subject: Regarding issues facing on NIFI Remote process group Hi NIFI Team, I am reaching out to you for the information regarding Remote process group. Please find the below details about NIFI and system setup we are using: NIFI version: 1.21.0 Environment details: 3 NIFI clusters for 2 NIFI servers and one NIFI client with 1TB storage. Each cluster have 3 instances of NIFI. use case: * We are having three NIFI clusters, where remote process group is running in one cluster which is RDC site(site-to-site NIFI client), SiteA (site-to-site NIFI server 1) and SiteB (site-to-site nifi server 2). * From SiteA and SiteB, only one NIFI server is reachable. If one goes down the other will starts working. Here SiteA NIFI server is currently running and RDC NIFI client is able to do data transmission between RDC NIFI client and SiteA nifi server. * When SiteA NIFI server goes down we are trying to update the SiteB nifi server URLs to expect site-to-site communication between RDC NIFI client and SiteB NIFI server. Problem statement: * Unable to stop the remote process group manually from NIFI UI to update the URLs of SiteB. * Observed once SiteA is not reachable, the remote process group in RDC NIFI client were not accepting any request ie., stop, edit, delete. Note: Three NIFI clusters are in three different environments. * Observed once we start SiteA NIFI server process we can able to stop the remote process group running in RDC client and able to update the URLs with SiteB NIFI server URLs. * If SiteA NIFI is not reachable then we are observing this issue in RDC NIFI client where unable to remote process group to update URLs. Expectation: User should able to stop, edit or delete the Remote process group running in RDC NIFI client when the NIFI server which is communicating with RDC NIFI client becomes unreachable. Please find the attachments of Remote process group highlighting the state of it. Apologise if there is any confusion created in the explanation. Need inputs to understand more to resolve the above issue. Please let us know if there is any other information needed. Thaks & Regards, Dharani Tirumanyam.
[ANNOUNCE] Apache NiFi 1.27.0 Released
Apache NiFi is an easy to use, powerful, and reliable system to process and distribute data. https://nifi.apache.org The release artifacts can be downloaded from the project website. https://nifi.apache.org/download/ Maven artifacts have been released and mirrored according to ASF artifact distribution processes. Issues resolved in Apache NiFi 1.27.0 are listed in Jira Release Notes. https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354832 Highlights of the release are available on the project wiki page: https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.27.0 Regards, The Apache NiFi Team
[RESULT][VOTE] Release Apache NiFi 1.27.0 (RC2)
Apache NiFi Community, I am pleased to announce that the 1.27.0 release of Apache NiFi passes: 7 +1 (binding) votes 4 +1 (non-binding) votes 0 0 votes 0 -1 votes Thanks to all who helped make this release possible! The release artifacts will be published in the next 24 hours. Here is the vote thread: https://lists.apache.org/thread/f2vs42o32h8065xxbloc6fooy2j3s8mj Thanks, Pierre
Re: [VOTE] Release Apache NiFi 1.27.0 (RC2)
+1 binding - closing the vote, thanks all! Le sam. 6 juil. 2024 à 13:58, Peter Turcsanyi a écrit : > +1 (binding) > > Verified signatures and hashes. > > Built NiFi on Ubuntu 22.04 with Java 8 (Zulu 1.8.0_412-b08) and Java 11 > (Zulu 11.0.23+9-LTS), Maven 3.9.8 with empty local repo. > > Started up NiFi in secure / unsecure mode on Java 8 / 11. > > Ran flows for validating: > - NIFI-13181 Azure Blob and ADLS processors throw NoSuchMethodError when > Service Principal is used > - NIFI-12231 Add completion strategy to FetchSmb > > Thanks for RMing Pierre! > > Regards, > Peter Turcsanyi > > On Fri, Jul 5, 2024 at 10:00 PM Csaba Bejan wrote: > > > +1 (binding) > > > >- Went through the helper guide and did a clean build > >- Verified signatures and hashes > >- Built on OSX 14.2.1 > >- Java version: 11.0.20, OpenJDK 64-Bit Server VM Zulu11.66+15-CA > (build > >11.0.20+8-LTS, mixed mode) > >- Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546) > >- Started NiFi and created a simple flow > >- Started MiNiFi and verified integration with C2 Server. Played > around > >with the C2 protocol (Operations - Update, Transfer, Describe...) > > > > Thanks for RMing, Pierre! > > > > Regards, > > > > Csaba > > > > On Fri, Jul 5, 2024 at 2:30 PM Matt Burgess > wrote: > > > > > +1 (binding) ran through the release helper and tested various flows > > > including NIFI-13422. > > > > > > Apache Maven 3.9.8 (36645f6c9b5079805ea5009217e36f2cffd34256) > > > Java version: 1.8.0_372, vendor: Azul Systems, Inc., runtime: > > > > > > > > > /Users/mburgess/.sdkman/candidates/java/8.0.372-zulu/zulu-8.jdk/Contents/Home/jre > > > Default locale: en_US, platform encoding: UTF-8 > > > OS name: "mac os x", version: "14.5", arch: "aarch64", family: "mac" > > > > > > Thanks for RM'ing Pierre! > > > > > > On Wed, Jul 3, 2024 at 9:01 AM Pierre Villard < > > pierre.villard...@gmail.com > > > > > > > wrote: > > > > > > > Team, > > > > > > > > I am pleased to be calling this vote for the source release of Apache > > > NiFi > > > > 1.27.0. > > > > > > > > Please review the following guide for how to verify a release > candidate > > > > build: > > > > > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification > > > > > > > > The source being voted on the and the convenience binaries are > > available > > > on > > > > the Apache Distribution Repository: > > > > > > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.27.0 > > > > > > > > The build artifacts are available on the Apache Nexus Repository: > > > > > > > > > https://repository.apache.org/content/repositories/orgapachenifi-1276 > > > > > > > > Git Tag: nifi-1.27.0-RC2 > > > > Git Commit ID: e0c4461d90bd4f6e5f2b81765bcff5cd97ed3e18 > > > > GitHub Commit Link: > > > > > > > > > > > > > > https://github.com/apache/nifi/commit/e0c4461d90bd4f6e5f2b81765bcff5cd97ed3e18 > > > > > > > > Checksums of nifi-1.27.0-source-release.zip > > > > > > > > SHA256: > > 0ac01d54eeceb4a4f4863880bf67dfa71e6a585036c5caf0546c592bf55ced48 > > > > SHA512: > > > > > > > > > > > > > > 675c7750752bf3092061c9eaac39a975955e9bf881e6bee3124c5842738d8c8626b6a551f33ef7a678018bd83e0323c1f0f0d79101255494d8ca91be7fc750f5 > > > > > > > > Release artifacts are signed with the following key: > > > > > > > > https://people.apache.org/keys/committer/pvillard.asc > > > > > > > > KEYS file is available on the Apache Distribution Repository: > > > > > > > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > > > > > Issues resolved for this version: 37 > > > > > > > > > > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354832 > > > > > > > > Release note highlights can be found on the project wiki: > > > > > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.27.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. > > Then > > > > please vote: > > > > > > > > [] +1 Release this package as nifi-1.27.0 > > > > [] +0 no opinion > > > > [] -1 Do not release this package because... > > > > > > > > > >
Re: [VOTE] Release Apache NiFi 1.27.0 (RC2)
+1 (binding) Verified signatures and hashes. Built NiFi on Ubuntu 22.04 with Java 8 (Zulu 1.8.0_412-b08) and Java 11 (Zulu 11.0.23+9-LTS), Maven 3.9.8 with empty local repo. Started up NiFi in secure / unsecure mode on Java 8 / 11. Ran flows for validating: - NIFI-13181 Azure Blob and ADLS processors throw NoSuchMethodError when Service Principal is used - NIFI-12231 Add completion strategy to FetchSmb Thanks for RMing Pierre! Regards, Peter Turcsanyi On Fri, Jul 5, 2024 at 10:00 PM Csaba Bejan wrote: > +1 (binding) > >- Went through the helper guide and did a clean build >- Verified signatures and hashes >- Built on OSX 14.2.1 >- Java version: 11.0.20, OpenJDK 64-Bit Server VM Zulu11.66+15-CA (build >11.0.20+8-LTS, mixed mode) >- Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546) >- Started NiFi and created a simple flow >- Started MiNiFi and verified integration with C2 Server. Played around >with the C2 protocol (Operations - Update, Transfer, Describe...) > > Thanks for RMing, Pierre! > > Regards, > > Csaba > > On Fri, Jul 5, 2024 at 2:30 PM Matt Burgess wrote: > > > +1 (binding) ran through the release helper and tested various flows > > including NIFI-13422. > > > > Apache Maven 3.9.8 (36645f6c9b5079805ea5009217e36f2cffd34256) > > Java version: 1.8.0_372, vendor: Azul Systems, Inc., runtime: > > > > > /Users/mburgess/.sdkman/candidates/java/8.0.372-zulu/zulu-8.jdk/Contents/Home/jre > > Default locale: en_US, platform encoding: UTF-8 > > OS name: "mac os x", version: "14.5", arch: "aarch64", family: "mac" > > > > Thanks for RM'ing Pierre! > > > > On Wed, Jul 3, 2024 at 9:01 AM Pierre Villard < > pierre.villard...@gmail.com > > > > > wrote: > > > > > Team, > > > > > > I am pleased to be calling this vote for the source release of Apache > > NiFi > > > 1.27.0. > > > > > > Please review the following guide for how to verify a release candidate > > > build: > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification > > > > > > The source being voted on the and the convenience binaries are > available > > on > > > the Apache Distribution Repository: > > > > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.27.0 > > > > > > The build artifacts are available on the Apache Nexus Repository: > > > > > > https://repository.apache.org/content/repositories/orgapachenifi-1276 > > > > > > Git Tag: nifi-1.27.0-RC2 > > > Git Commit ID: e0c4461d90bd4f6e5f2b81765bcff5cd97ed3e18 > > > GitHub Commit Link: > > > > > > > > > https://github.com/apache/nifi/commit/e0c4461d90bd4f6e5f2b81765bcff5cd97ed3e18 > > > > > > Checksums of nifi-1.27.0-source-release.zip > > > > > > SHA256: > 0ac01d54eeceb4a4f4863880bf67dfa71e6a585036c5caf0546c592bf55ced48 > > > SHA512: > > > > > > > > > 675c7750752bf3092061c9eaac39a975955e9bf881e6bee3124c5842738d8c8626b6a551f33ef7a678018bd83e0323c1f0f0d79101255494d8ca91be7fc750f5 > > > > > > Release artifacts are signed with the following key: > > > > > > https://people.apache.org/keys/committer/pvillard.asc > > > > > > KEYS file is available on the Apache Distribution Repository: > > > > > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > > > Issues resolved for this version: 37 > > > > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354832 > > > > > > Release note highlights can be found on the project wiki: > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.27.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. > Then > > > please vote: > > > > > > [] +1 Release this package as nifi-1.27.0 > > > [] +0 no opinion > > > [] -1 Do not release this package because... > > > > > >
Re: [VOTE] Release Apache NiFi 1.27.0 (RC2)
+1 (binding) - Went through the helper guide and did a clean build - Verified signatures and hashes - Built on OSX 14.2.1 - Java version: 11.0.20, OpenJDK 64-Bit Server VM Zulu11.66+15-CA (build 11.0.20+8-LTS, mixed mode) - Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546) - Started NiFi and created a simple flow - Started MiNiFi and verified integration with C2 Server. Played around with the C2 protocol (Operations - Update, Transfer, Describe...) Thanks for RMing, Pierre! Regards, Csaba On Fri, Jul 5, 2024 at 2:30 PM Matt Burgess wrote: > +1 (binding) ran through the release helper and tested various flows > including NIFI-13422. > > Apache Maven 3.9.8 (36645f6c9b5079805ea5009217e36f2cffd34256) > Java version: 1.8.0_372, vendor: Azul Systems, Inc., runtime: > > /Users/mburgess/.sdkman/candidates/java/8.0.372-zulu/zulu-8.jdk/Contents/Home/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "14.5", arch: "aarch64", family: "mac" > > Thanks for RM'ing Pierre! > > On Wed, Jul 3, 2024 at 9:01 AM Pierre Villard > > wrote: > > > Team, > > > > I am pleased to be calling this vote for the source release of Apache > NiFi > > 1.27.0. > > > > Please review the following guide for how to verify a release candidate > > build: > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification > > > > The source being voted on the and the convenience binaries are available > on > > the Apache Distribution Repository: > > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.27.0 > > > > The build artifacts are available on the Apache Nexus Repository: > > > > https://repository.apache.org/content/repositories/orgapachenifi-1276 > > > > Git Tag: nifi-1.27.0-RC2 > > Git Commit ID: e0c4461d90bd4f6e5f2b81765bcff5cd97ed3e18 > > GitHub Commit Link: > > > > > https://github.com/apache/nifi/commit/e0c4461d90bd4f6e5f2b81765bcff5cd97ed3e18 > > > > Checksums of nifi-1.27.0-source-release.zip > > > > SHA256: 0ac01d54eeceb4a4f4863880bf67dfa71e6a585036c5caf0546c592bf55ced48 > > SHA512: > > > > > 675c7750752bf3092061c9eaac39a975955e9bf881e6bee3124c5842738d8c8626b6a551f33ef7a678018bd83e0323c1f0f0d79101255494d8ca91be7fc750f5 > > > > Release artifacts are signed with the following key: > > > > https://people.apache.org/keys/committer/pvillard.asc > > > > KEYS file is available on the Apache Distribution Repository: > > > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > Issues resolved for this version: 37 > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354832 > > > > Release note highlights can be found on the project wiki: > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.27.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. Then > > please vote: > > > > [] +1 Release this package as nifi-1.27.0 > > [] +0 no opinion > > [] -1 Do not release this package because... > > >
Re: [VOTE] Release Apache NiFi 1.27.0 (RC2)
+1 (binding) ran through the release helper and tested various flows including NIFI-13422. Apache Maven 3.9.8 (36645f6c9b5079805ea5009217e36f2cffd34256) Java version: 1.8.0_372, vendor: Azul Systems, Inc., runtime: /Users/mburgess/.sdkman/candidates/java/8.0.372-zulu/zulu-8.jdk/Contents/Home/jre Default locale: en_US, platform encoding: UTF-8 OS name: "mac os x", version: "14.5", arch: "aarch64", family: "mac" Thanks for RM'ing Pierre! On Wed, Jul 3, 2024 at 9:01 AM Pierre Villard wrote: > Team, > > I am pleased to be calling this vote for the source release of Apache NiFi > 1.27.0. > > Please review the following guide for how to verify a release candidate > build: > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification > > The source being voted on the and the convenience binaries are available on > the Apache Distribution Repository: > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.27.0 > > The build artifacts are available on the Apache Nexus Repository: > > https://repository.apache.org/content/repositories/orgapachenifi-1276 > > Git Tag: nifi-1.27.0-RC2 > Git Commit ID: e0c4461d90bd4f6e5f2b81765bcff5cd97ed3e18 > GitHub Commit Link: > > https://github.com/apache/nifi/commit/e0c4461d90bd4f6e5f2b81765bcff5cd97ed3e18 > > Checksums of nifi-1.27.0-source-release.zip > > SHA256: 0ac01d54eeceb4a4f4863880bf67dfa71e6a585036c5caf0546c592bf55ced48 > SHA512: > > 675c7750752bf3092061c9eaac39a975955e9bf881e6bee3124c5842738d8c8626b6a551f33ef7a678018bd83e0323c1f0f0d79101255494d8ca91be7fc750f5 > > Release artifacts are signed with the following key: > > https://people.apache.org/keys/committer/pvillard.asc > > KEYS file is available on the Apache Distribution Repository: > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > Issues resolved for this version: 37 > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354832 > > Release note highlights can be found on the project wiki: > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.27.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. Then > please vote: > > [] +1 Release this package as nifi-1.27.0 > [] +0 no opinion > [] -1 Do not release this package because... >
Re: [VOTE] Release Apache NiFi 1.27.0 (RC2)
+1 (non-binding) - went through the helper guide, - did a full build with contrib check - verified signatures and hashes Environment: - macOS Version 14.3.1 - OpenJDK Runtime Environment (Zulu 8.62.0.19-CA-macos-aarch64) (build 1.8.0_332-b09) - Apache Maven 3.9.6 Created and ran some simple flows. Verified the following tickets: - NIFI-13478: Protobuf Reader fails to coerce type of repeated fields - NIFI-13356 Fixed ProtobufReader handling of repeated fields Thanks for RMing Pierre! Regards, Mark Ferenc Kis ezt írta (időpont: 2024. júl. 5., P, 14:21): > +1 (non-binding) > > Went through the helper guide, local maven repo cleaned up, full clean > build with contrib check, verified signatures and hashes > > Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae) > Maven home: /Users/fkis/.sdkman/candidates/maven/current > Java version: 1.8.0_362, vendor: Azul Systems, Inc., runtime: > > /Users/fkis/.sdkman/candidates/java/8.0.362-zulu/zulu-8.jdk/Contents/Home/jre > Default locale: en_HU, platform encoding: UTF-8 > OS name: "mac os x", version: "14.5", arch: "aarch64", family: "mac" > > Validations performed: > - Started NiFi, created a simple flow with ListenHTTP and Input Port. > Validated ListenHTTP processor is able to receive data > - Started MiNiFi Java: > * created a simple GenerateFlowFile -> InvokeHttp flow and > GenerateFlowFile -> RemoteProcessGroup flow and pushed to MiNiFi via C2 > protocol. > * Validated that connectivity between NiFi and MiNiFi works via both > InvokeHTTP and S2S > > Thanks for RMing Pierre! > > Regards > Ferenc > > On Thu, Jul 4, 2024 at 10:29 PM Joe Witt wrote: > > > +1 binding > > > > On Thu, Jul 4, 2024 at 1:28 PM David Handermann < > > exceptionfact...@apache.org> > > wrote: > > > > > +1 binding > > > > > > - Verified signatures and hashes > > > - Ran build using Maven Wrapper 3.9.6 > > > - Ran build on Ubuntu 22.04 with Azul Zulu JDK 1.8.0-412 x86_64 > > > - Ran build on Ubuntu 22.04 with Azul Zulu JDK 17.0.11 x86_64 > > > - Ran NiFi on Ubuntu 22.04 with Azul Zulu JDK 17.0.11 x86_64 > > > - Ran NiFi on macOS 14.5 with Azul Zulu JDK 21.0.1 Aarch64 > > > - Ran NiFi Registry on Ubuntu 22.04 with Azul Zulu JDK 17.0.11 x86_64 > > > > > > - Verified NIFI-13429 with EncryptContentPGP and DecryptContentPGP > > > using sample JPEG > > > - Verified NIFI-13464 NiFi Registry starts without issues following > > > deprecation-log dependency adjustments > > > > > > Thanks Pierre! > > > > > > Regards, > > > David Handermann > > > > > > On Wed, Jul 3, 2024 at 7:42 AM Pierre Villard > > > wrote: > > > > > > > > Team, > > > > > > > > I am pleased to be calling this vote for the source release of Apache > > > NiFi > > > > 1.27.0. > > > > > > > > Please review the following guide for how to verify a release > candidate > > > > build: > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification > > > > > > > > The source being voted on the and the convenience binaries are > > available > > > on > > > > the Apache Distribution Repository: > > > > > > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.27.0 > > > > > > > > The build artifacts are available on the Apache Nexus Repository: > > > > > > > > > https://repository.apache.org/content/repositories/orgapachenifi-1276 > > > > > > > > Git Tag: nifi-1.27.0-RC2 > > > > Git Commit ID: e0c4461d90bd4f6e5f2b81765bcff5cd97ed3e18 > > > > GitHub Commit Link: > > > > > > > > > > https://github.com/apache/nifi/commit/e0c4461d90bd4f6e5f2b81765bcff5cd97ed3e18 > > > > > > > > Checksums of nifi-1.27.0-source-release.zip > > > > > > > > SHA256: > > 0ac01d54eeceb4a4f4863880bf67dfa71e6a585036c5caf0546c592bf55ced48 > > > > SHA512: > > > > > > > > > > 675c7750752bf3092061c9eaac39a975955e9bf881e6bee3124c5842738d8c8626b6a551f33ef7a678018bd83e0323c1f0f0d79101255494d8ca91be7fc750f5 > > > > > > > > Release artifacts are signed with the following key: > > > > > > > > https://people.apache.org/keys/committer/pvillard.asc > > > > > > > > KEYS file is available on the Apache Distribution Repository: > > > > > > > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > > > > > Issues resolved for this version: 37 > > > > > > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354832 > > > > > > > > Release note highlights can be found on the project wiki: > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.27.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. > > Then > > > > please vote: > > > > > > > > [] +1 Release this package as nifi-1.27.0 > > > > [] +0 no opinion > > > > [] -1 Do not release this package because... > > > > > >
Re: [VOTE] Release Apache NiFi 1.27.0 (RC2)
+1 (non-binding) Went through the helper guide, local maven repo cleaned up, full clean build with contrib check, verified signatures and hashes Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae) Maven home: /Users/fkis/.sdkman/candidates/maven/current Java version: 1.8.0_362, vendor: Azul Systems, Inc., runtime: /Users/fkis/.sdkman/candidates/java/8.0.362-zulu/zulu-8.jdk/Contents/Home/jre Default locale: en_HU, platform encoding: UTF-8 OS name: "mac os x", version: "14.5", arch: "aarch64", family: "mac" Validations performed: - Started NiFi, created a simple flow with ListenHTTP and Input Port. Validated ListenHTTP processor is able to receive data - Started MiNiFi Java: * created a simple GenerateFlowFile -> InvokeHttp flow and GenerateFlowFile -> RemoteProcessGroup flow and pushed to MiNiFi via C2 protocol. * Validated that connectivity between NiFi and MiNiFi works via both InvokeHTTP and S2S Thanks for RMing Pierre! Regards Ferenc On Thu, Jul 4, 2024 at 10:29 PM Joe Witt wrote: > +1 binding > > On Thu, Jul 4, 2024 at 1:28 PM David Handermann < > exceptionfact...@apache.org> > wrote: > > > +1 binding > > > > - Verified signatures and hashes > > - Ran build using Maven Wrapper 3.9.6 > > - Ran build on Ubuntu 22.04 with Azul Zulu JDK 1.8.0-412 x86_64 > > - Ran build on Ubuntu 22.04 with Azul Zulu JDK 17.0.11 x86_64 > > - Ran NiFi on Ubuntu 22.04 with Azul Zulu JDK 17.0.11 x86_64 > > - Ran NiFi on macOS 14.5 with Azul Zulu JDK 21.0.1 Aarch64 > > - Ran NiFi Registry on Ubuntu 22.04 with Azul Zulu JDK 17.0.11 x86_64 > > > > - Verified NIFI-13429 with EncryptContentPGP and DecryptContentPGP > > using sample JPEG > > - Verified NIFI-13464 NiFi Registry starts without issues following > > deprecation-log dependency adjustments > > > > Thanks Pierre! > > > > Regards, > > David Handermann > > > > On Wed, Jul 3, 2024 at 7:42 AM Pierre Villard > > wrote: > > > > > > Team, > > > > > > I am pleased to be calling this vote for the source release of Apache > > NiFi > > > 1.27.0. > > > > > > Please review the following guide for how to verify a release candidate > > > build: > > > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification > > > > > > The source being voted on the and the convenience binaries are > available > > on > > > the Apache Distribution Repository: > > > > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.27.0 > > > > > > The build artifacts are available on the Apache Nexus Repository: > > > > > > https://repository.apache.org/content/repositories/orgapachenifi-1276 > > > > > > Git Tag: nifi-1.27.0-RC2 > > > Git Commit ID: e0c4461d90bd4f6e5f2b81765bcff5cd97ed3e18 > > > GitHub Commit Link: > > > > > > https://github.com/apache/nifi/commit/e0c4461d90bd4f6e5f2b81765bcff5cd97ed3e18 > > > > > > Checksums of nifi-1.27.0-source-release.zip > > > > > > SHA256: > 0ac01d54eeceb4a4f4863880bf67dfa71e6a585036c5caf0546c592bf55ced48 > > > SHA512: > > > > > > 675c7750752bf3092061c9eaac39a975955e9bf881e6bee3124c5842738d8c8626b6a551f33ef7a678018bd83e0323c1f0f0d79101255494d8ca91be7fc750f5 > > > > > > Release artifacts are signed with the following key: > > > > > > https://people.apache.org/keys/committer/pvillard.asc > > > > > > KEYS file is available on the Apache Distribution Repository: > > > > > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > > > Issues resolved for this version: 37 > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354832 > > > > > > Release note highlights can be found on the project wiki: > > > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.27.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. > Then > > > please vote: > > > > > > [] +1 Release this package as nifi-1.27.0 > > > [] +0 no opinion > > > [] -1 Do not release this package because... > > >
Re: [VOTE] Release Apache NiFi 1.27.0 (RC2)
+1 binding On Thu, Jul 4, 2024 at 1:28 PM David Handermann wrote: > +1 binding > > - Verified signatures and hashes > - Ran build using Maven Wrapper 3.9.6 > - Ran build on Ubuntu 22.04 with Azul Zulu JDK 1.8.0-412 x86_64 > - Ran build on Ubuntu 22.04 with Azul Zulu JDK 17.0.11 x86_64 > - Ran NiFi on Ubuntu 22.04 with Azul Zulu JDK 17.0.11 x86_64 > - Ran NiFi on macOS 14.5 with Azul Zulu JDK 21.0.1 Aarch64 > - Ran NiFi Registry on Ubuntu 22.04 with Azul Zulu JDK 17.0.11 x86_64 > > - Verified NIFI-13429 with EncryptContentPGP and DecryptContentPGP > using sample JPEG > - Verified NIFI-13464 NiFi Registry starts without issues following > deprecation-log dependency adjustments > > Thanks Pierre! > > Regards, > David Handermann > > On Wed, Jul 3, 2024 at 7:42 AM Pierre Villard > wrote: > > > > Team, > > > > I am pleased to be calling this vote for the source release of Apache > NiFi > > 1.27.0. > > > > Please review the following guide for how to verify a release candidate > > build: > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification > > > > The source being voted on the and the convenience binaries are available > on > > the Apache Distribution Repository: > > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.27.0 > > > > The build artifacts are available on the Apache Nexus Repository: > > > > https://repository.apache.org/content/repositories/orgapachenifi-1276 > > > > Git Tag: nifi-1.27.0-RC2 > > Git Commit ID: e0c4461d90bd4f6e5f2b81765bcff5cd97ed3e18 > > GitHub Commit Link: > > > https://github.com/apache/nifi/commit/e0c4461d90bd4f6e5f2b81765bcff5cd97ed3e18 > > > > Checksums of nifi-1.27.0-source-release.zip > > > > SHA256: 0ac01d54eeceb4a4f4863880bf67dfa71e6a585036c5caf0546c592bf55ced48 > > SHA512: > > > 675c7750752bf3092061c9eaac39a975955e9bf881e6bee3124c5842738d8c8626b6a551f33ef7a678018bd83e0323c1f0f0d79101255494d8ca91be7fc750f5 > > > > Release artifacts are signed with the following key: > > > > https://people.apache.org/keys/committer/pvillard.asc > > > > KEYS file is available on the Apache Distribution Repository: > > > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > Issues resolved for this version: 37 > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354832 > > > > Release note highlights can be found on the project wiki: > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.27.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. Then > > please vote: > > > > [] +1 Release this package as nifi-1.27.0 > > [] +0 no opinion > > [] -1 Do not release this package because... >
Re: [VOTE] Release Apache NiFi 1.27.0 (RC2)
+1 binding - Verified signatures and hashes - Ran build using Maven Wrapper 3.9.6 - Ran build on Ubuntu 22.04 with Azul Zulu JDK 1.8.0-412 x86_64 - Ran build on Ubuntu 22.04 with Azul Zulu JDK 17.0.11 x86_64 - Ran NiFi on Ubuntu 22.04 with Azul Zulu JDK 17.0.11 x86_64 - Ran NiFi on macOS 14.5 with Azul Zulu JDK 21.0.1 Aarch64 - Ran NiFi Registry on Ubuntu 22.04 with Azul Zulu JDK 17.0.11 x86_64 - Verified NIFI-13429 with EncryptContentPGP and DecryptContentPGP using sample JPEG - Verified NIFI-13464 NiFi Registry starts without issues following deprecation-log dependency adjustments Thanks Pierre! Regards, David Handermann On Wed, Jul 3, 2024 at 7:42 AM Pierre Villard wrote: > > Team, > > I am pleased to be calling this vote for the source release of Apache NiFi > 1.27.0. > > Please review the following guide for how to verify a release candidate > build: > > https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification > > The source being voted on the and the convenience binaries are available on > the Apache Distribution Repository: > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.27.0 > > The build artifacts are available on the Apache Nexus Repository: > > https://repository.apache.org/content/repositories/orgapachenifi-1276 > > Git Tag: nifi-1.27.0-RC2 > Git Commit ID: e0c4461d90bd4f6e5f2b81765bcff5cd97ed3e18 > GitHub Commit Link: > https://github.com/apache/nifi/commit/e0c4461d90bd4f6e5f2b81765bcff5cd97ed3e18 > > Checksums of nifi-1.27.0-source-release.zip > > SHA256: 0ac01d54eeceb4a4f4863880bf67dfa71e6a585036c5caf0546c592bf55ced48 > SHA512: > 675c7750752bf3092061c9eaac39a975955e9bf881e6bee3124c5842738d8c8626b6a551f33ef7a678018bd83e0323c1f0f0d79101255494d8ca91be7fc750f5 > > Release artifacts are signed with the following key: > > https://people.apache.org/keys/committer/pvillard.asc > > KEYS file is available on the Apache Distribution Repository: > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > Issues resolved for this version: 37 > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354832 > > Release note highlights can be found on the project wiki: > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.27.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. Then > please vote: > > [] +1 Release this package as nifi-1.27.0 > [] +0 no opinion > [] -1 Do not release this package because...
Re: Nifi 2.0.0 Major release timeline
Ajay We do not have a specific date in mind. I believe largely we've completed the major efforts we had intended for 2.0 and that even went further to include a completely re-written UI which is a huge help. We do continue to find unmaintained or security relevant code with limited maintenance and we're aggressively cleaning all that up. We need to ensure we've cleaned up all deprecated bits and are putting ourselves in the best position to maintain, secure, and add capability as we go. Not speaking for the community but my personal take is we're likely 1-2 months away now from minting a release as GA of 2.0 as what I see that remains is pretty purely just code removal/clean-up. There are always one or two surprises that emerge but the 2.0 line is looking really good and is already considerably in use for production purposes so stability is there. Thanks Joe On Thu, Jul 4, 2024 at 6:16 AM Premarajan, Ajay wrote: > Hi Team, > > We are currently using NiFi version 1.26 in our production environment. Is > there a scheduled timeline for the major release of NiFi 2.0.0, or an > estimate of how many milestone releases are planned before the major > version is released? > > > Mit freundlichen Grüßen / Kind regards > > Ajay Premarajan > >
Nifi 2.0.0 Major release timeline
Hi Team, We are currently using NiFi version 1.26 in our production environment. Is there a scheduled timeline for the major release of NiFi 2.0.0, or an estimate of how many milestone releases are planned before the major version is released? Mit freundlichen Grüßen / Kind regards Ajay Premarajan
Re: [VOTE] Release Apache NiFi 1.27.0 (RC2)
+1 (binding) - Verified hashes and signatures - Successfully built NiFi 1.27.0 with contrib-check in the following environment: - Ubuntu 22.04 6.5.0-41-generic - Java version: 11.0.23 - Apache Maven 3.9.6 - Successfully designed and ran a simple flow - Tested S2S communication and HTTP data forwarding from MiNiFi C++ - Tested MiNiFi-C2 server with MiNiFi C++ Thanks Pierre for RMing! Best Regards, Gabor On Wed, 3 Jul 2024 at 22:27, Dan S wrote: > > +1 (non-binding) > Ran through Release Candidate Verification > Verified signatures and hashes > Built with: > > Maven home: /opt/apache-maven-3.9.6 > Java version: 1.8.0_412, vendor: Red Hat, Inc., runtime: > /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.412.b08-2.el8.x86_64/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "4.18.0-513.24.1.el8_9.x86_64", arch: "amd64", > family: "unix" > > Exercised new feature NIFI-13304 SplitExcel > > Thanks for RM'ing Pierre! > > > On Wed, Jul 3, 2024 at 12:07 PM Nissim Shiman > wrote: > > > +1 (non-binding) > > > > checksums are good > > > > Compiled with > > Apache Maven 3.9.6 1.8.0_412 (openjdk) RHEL 8 > > > > Ran some basic flows Upgraded registry (with pre-existing versioned > > flows) from 1.26 to 1.27 successfully. Created new PGs from versioned > > flows. Pushed new versions of flows to registry. > > > > > > Discovered issue where nifi will not recognize versioned PG has been > > modified if modification was done to versioned inner PG. > > Created https://issues.apache.org/jira/browse/NIFI-13486 > > This is not a blocker level issue (and further review found it existed in > > 1.26 as well.) > > > > > > Thank you Pierre and team for the upcoming release. > > > > > > Thanks, > > Nissim Shiman > > > > > > On Wednesday, July 3, 2024 at 12:42:40 PM UTC, Pierre Villard < > > pierre.villard...@gmail.com> wrote: > > > > Team, > > > > I am pleased to be calling this vote for the source release of Apache NiFi > > 1.27.0. > > > > Please review the following guide for how to verify a release candidate > > build: > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification > > > > The source being voted on the and the convenience binaries are available on > > the Apache Distribution Repository: > > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.27.0 > > > > The build artifacts are available on the Apache Nexus Repository: > > > > https://repository.apache.org/content/repositories/orgapachenifi-1276 > > > > Git Tag: nifi-1.27.0-RC2 > > Git Commit ID: e0c4461d90bd4f6e5f2b81765bcff5cd97ed3e18 > > GitHub Commit Link: > > > > https://github.com/apache/nifi/commit/e0c4461d90bd4f6e5f2b81765bcff5cd97ed3e18 > > > > Checksums of nifi-1.27.0-source-release.zip > > > > SHA256: 0ac01d54eeceb4a4f4863880bf67dfa71e6a585036c5caf0546c592bf55ced48 > > SHA512: > > > > 675c7750752bf3092061c9eaac39a975955e9bf881e6bee3124c5842738d8c8626b6a551f33ef7a678018bd83e0323c1f0f0d79101255494d8ca91be7fc750f5 > > > > Release artifacts are signed with the following key: > > > > https://people.apache.org/keys/committer/pvillard.asc > > > > KEYS file is available on the Apache Distribution Repository: > > > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > Issues resolved for this version: 37 > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354832 > > > > Release note highlights can be found on the project wiki: > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.27.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. Then > > please vote: > > > > [] +1 Release this package as nifi-1.27.0 > > [] +0 no opinion > > [] -1 Do not release this package because... > >
Re: [VOTE] Release Apache NiFi 1.27.0 (RC2)
+1 (non-binding) Ran through Release Candidate Verification Verified signatures and hashes Built with: Maven home: /opt/apache-maven-3.9.6 Java version: 1.8.0_412, vendor: Red Hat, Inc., runtime: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.412.b08-2.el8.x86_64/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "4.18.0-513.24.1.el8_9.x86_64", arch: "amd64", family: "unix" Exercised new feature NIFI-13304 SplitExcel Thanks for RM'ing Pierre! On Wed, Jul 3, 2024 at 12:07 PM Nissim Shiman wrote: > +1 (non-binding) > > checksums are good > > Compiled with > Apache Maven 3.9.6 1.8.0_412 (openjdk) RHEL 8 > > Ran some basic flows Upgraded registry (with pre-existing versioned > flows) from 1.26 to 1.27 successfully. Created new PGs from versioned > flows. Pushed new versions of flows to registry. > > > Discovered issue where nifi will not recognize versioned PG has been > modified if modification was done to versioned inner PG. > Created https://issues.apache.org/jira/browse/NIFI-13486 > This is not a blocker level issue (and further review found it existed in > 1.26 as well.) > > > Thank you Pierre and team for the upcoming release. > > > Thanks, > Nissim Shiman > > > On Wednesday, July 3, 2024 at 12:42:40 PM UTC, Pierre Villard < > pierre.villard...@gmail.com> wrote: > > Team, > > I am pleased to be calling this vote for the source release of Apache NiFi > 1.27.0. > > Please review the following guide for how to verify a release candidate > build: > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification > > The source being voted on the and the convenience binaries are available on > the Apache Distribution Repository: > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.27.0 > > The build artifacts are available on the Apache Nexus Repository: > > https://repository.apache.org/content/repositories/orgapachenifi-1276 > > Git Tag: nifi-1.27.0-RC2 > Git Commit ID: e0c4461d90bd4f6e5f2b81765bcff5cd97ed3e18 > GitHub Commit Link: > > https://github.com/apache/nifi/commit/e0c4461d90bd4f6e5f2b81765bcff5cd97ed3e18 > > Checksums of nifi-1.27.0-source-release.zip > > SHA256: 0ac01d54eeceb4a4f4863880bf67dfa71e6a585036c5caf0546c592bf55ced48 > SHA512: > > 675c7750752bf3092061c9eaac39a975955e9bf881e6bee3124c5842738d8c8626b6a551f33ef7a678018bd83e0323c1f0f0d79101255494d8ca91be7fc750f5 > > Release artifacts are signed with the following key: > > https://people.apache.org/keys/committer/pvillard.asc > > KEYS file is available on the Apache Distribution Repository: > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > Issues resolved for this version: 37 > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354832 > > Release note highlights can be found on the project wiki: > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.27.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. Then > please vote: > > [] +1 Release this package as nifi-1.27.0 > [] +0 no opinion > [] -1 Do not release this package because... >
Re: [VOTE] Release Apache NiFi 1.27.0 (RC2)
+1 (non-binding) checksums are good Compiled with Apache Maven 3.9.6 1.8.0_412 (openjdk) RHEL 8 Ran some basic flows Upgraded registry (with pre-existing versioned flows) from 1.26 to 1.27 successfully. Created new PGs from versioned flows. Pushed new versions of flows to registry. Discovered issue where nifi will not recognize versioned PG has been modified if modification was done to versioned inner PG. Created https://issues.apache.org/jira/browse/NIFI-13486 This is not a blocker level issue (and further review found it existed in 1.26 as well.) Thank you Pierre and team for the upcoming release. Thanks, Nissim Shiman On Wednesday, July 3, 2024 at 12:42:40 PM UTC, Pierre Villard wrote: Team, I am pleased to be calling this vote for the source release of Apache NiFi 1.27.0. Please review the following guide for how to verify a release candidate build: https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification The source being voted on the and the convenience binaries are available on the Apache Distribution Repository: https://dist.apache.org/repos/dist/dev/nifi/nifi-1.27.0 The build artifacts are available on the Apache Nexus Repository: https://repository.apache.org/content/repositories/orgapachenifi-1276 Git Tag: nifi-1.27.0-RC2 Git Commit ID: e0c4461d90bd4f6e5f2b81765bcff5cd97ed3e18 GitHub Commit Link: https://github.com/apache/nifi/commit/e0c4461d90bd4f6e5f2b81765bcff5cd97ed3e18 Checksums of nifi-1.27.0-source-release.zip SHA256: 0ac01d54eeceb4a4f4863880bf67dfa71e6a585036c5caf0546c592bf55ced48 SHA512: 675c7750752bf3092061c9eaac39a975955e9bf881e6bee3124c5842738d8c8626b6a551f33ef7a678018bd83e0323c1f0f0d79101255494d8ca91be7fc750f5 Release artifacts are signed with the following key: https://people.apache.org/keys/committer/pvillard.asc KEYS file is available on the Apache Distribution Repository: https://dist.apache.org/repos/dist/release/nifi/KEYS Issues resolved for this version: 37 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354832 Release note highlights can be found on the project wiki: https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.27.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. Then please vote: [] +1 Release this package as nifi-1.27.0 [] +0 no opinion [] -1 Do not release this package because...
[VOTE] Release Apache NiFi 1.27.0 (RC2)
Team, I am pleased to be calling this vote for the source release of Apache NiFi 1.27.0. Please review the following guide for how to verify a release candidate build: https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification The source being voted on the and the convenience binaries are available on the Apache Distribution Repository: https://dist.apache.org/repos/dist/dev/nifi/nifi-1.27.0 The build artifacts are available on the Apache Nexus Repository: https://repository.apache.org/content/repositories/orgapachenifi-1276 Git Tag: nifi-1.27.0-RC2 Git Commit ID: e0c4461d90bd4f6e5f2b81765bcff5cd97ed3e18 GitHub Commit Link: https://github.com/apache/nifi/commit/e0c4461d90bd4f6e5f2b81765bcff5cd97ed3e18 Checksums of nifi-1.27.0-source-release.zip SHA256: 0ac01d54eeceb4a4f4863880bf67dfa71e6a585036c5caf0546c592bf55ced48 SHA512: 675c7750752bf3092061c9eaac39a975955e9bf881e6bee3124c5842738d8c8626b6a551f33ef7a678018bd83e0323c1f0f0d79101255494d8ca91be7fc750f5 Release artifacts are signed with the following key: https://people.apache.org/keys/committer/pvillard.asc KEYS file is available on the Apache Distribution Repository: https://dist.apache.org/repos/dist/release/nifi/KEYS Issues resolved for this version: 37 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354832 Release note highlights can be found on the project wiki: https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.27.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. Then please vote: [] +1 Release this package as nifi-1.27.0 [] +0 no opinion [] -1 Do not release this package because...
Re: Regarding issues facing on NIFI Remote process group
Sorry for the spam, Please find the attachments here Thanks & Regards, Dharani Tirumanyam. From: Tirumanyam, Dharani Date: Monday, 1 July 2024 at 9:42 PM To: dev@nifi.apache.org Cc: Pulimi, Satish , Shankarprasad, Raghuveera , Tirumanyam, Dharani Subject: Regarding issues facing on NIFI Remote process group Hi NIFI Team, I am reaching out to you for the information regarding Remote process group. Please find the below details about NIFI and system setup we are using: NIFI version: 1.21.0 Environment details: 3 NIFI clusters for 2 NIFI servers and one NIFI client with 1TB storage. Each cluster have 3 instances of NIFI. use case: * We are having three NIFI clusters, where remote process group is running in one cluster which is RDC site(site-to-site NIFI client), SiteA (site-to-site NIFI server 1) and SiteB (site-to-site nifi server 2). * From SiteA and SiteB, only one NIFI server is reachable. If one goes down the other will starts working. Here SiteA NIFI server is currently running and RDC NIFI client is able to do data transmission between RDC NIFI client and SiteA nifi server. * When SiteA NIFI server goes down we are trying to update the SiteB nifi server URLs to expect site-to-site communication between RDC NIFI client and SiteB NIFI server. Problem statement: * Unable to stop the remote process group manually from NIFI UI to update the URLs of SiteB. * Observed once SiteA is not reachable, the remote process group in RDC NIFI client were not accepting any request ie., stop, edit, delete. Note: Three NIFI clusters are in three different environments. * Observed once we start SiteA NIFI server process we can able to stop the remote process group running in RDC client and able to update the URLs with SiteB NIFI server URLs. * If SiteA NIFI is not reachable then we are observing this issue in RDC NIFI client where unable to remote process group to update URLs. Expectation: User should able to stop, edit or delete the Remote process group running in RDC NIFI client when the NIFI server which is communicating with RDC NIFI client becomes unreachable. Please find the attachments of Remote process group highlighting the state of it. Apologise if there is any confusion created in the explanation. Need inputs to understand more to resolve the above issue. Please let us know if there is any other information needed. Thaks & Regards, Dharani Tirumanyam.
[ANNOUNCE] Apache NiFi 2.0.0-M4 Released
The Apache NiFi Team is pleased to announce the release of Apache NiFi 2.0.0-M4. Apache NiFi is an easy to use, powerful, and reliable system to process and distribute data. https://nifi.apache.org The release artifacts can be downloaded from the project website. https://nifi.apache.org/download/ Maven artifacts have been released and mirrored according to ASF artifact distribution processes. Issues resolved in Apache NiFi 2.0.0-M4 are listed in Jira Release Notes. https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354678 Highlights of the release are available on the project wiki page: https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0-M4 Regards, The Apache NiFi Team
Regarding issues facing on NIFI Remote process group
Hi NIFI Team, I am reaching out to you for the information regarding Remote process group. Please find the below details about NIFI and system setup we are using: NIFI version: 1.21.0 Environment details: 3 NIFI clusters for 2 NIFI servers and one NIFI client with 1TB storage. Each cluster have 3 instances of NIFI. use case: * We are having three NIFI clusters, where remote process group is running in one cluster which is RDC site(site-to-site NIFI client), SiteA (site-to-site NIFI server 1) and SiteB (site-to-site nifi server 2). * From SiteA and SiteB, only one NIFI server is reachable. If one goes down the other will starts working. Here SiteA NIFI server is currently running and RDC NIFI client is able to do data transmission between RDC NIFI client and SiteA nifi server. * When SiteA NIFI server goes down we are trying to update the SiteB nifi server URLs to expect site-to-site communication between RDC NIFI client and SiteB NIFI server. Problem statement: * Unable to stop the remote process group manually from NIFI UI to update the URLs of SiteB. * Observed once SiteA is not reachable, the remote process group in RDC NIFI client were not accepting any request ie., stop, edit, delete. Note: Three NIFI clusters are in three different environments. * Observed once we start SiteA NIFI server process we can able to stop the remote process group running in RDC client and able to update the URLs with SiteB NIFI server URLs. * If SiteA NIFI is not reachable then we are observing this issue in RDC NIFI client where unable to remote process group to update URLs. Expectation: User should able to stop, edit or delete the Remote process group running in RDC NIFI client when the NIFI server which is communicating with RDC NIFI client becomes unreachable. Please find the attachments of Remote process group highlighting the state of it. Apologise if there is any confusion created in the explanation. Need inputs to understand more to resolve the above issue. Please let us know if there is any other information needed. Thaks & Regards, Dharani Tirumanyam.
[RESULT][VOTE] Release Apache NiFi 2.0.0-M4 (RC1)
Apache NiFi Community, I am pleased to announce that the 2.0.0-M4 release of Apache NiFi passes: 6 +1 (binding) votes 4 +1 (non-binding) votes 0 0 votes 0 -1 votes Thanks to all who helped make this release possible! The release artifacts will be published in the next 24 hours. Here is the vote thread: https://lists.apache.org/thread/jdb2j398ow6221rx4og7p958nnbj7bs9 Regards, David Handermann
Re: [VOTE] Release Apache NiFi 2.0.0-M4 (RC1)
+1 (non-binding) - went through the helper guide, - did a full build with contrib check - verified signatures and hashes Environment: - macOS Version 14.3.1 - OpenJDK Runtime Environment Zulu21.28+85-CA (build 21+35) - Apache Maven 3.9.6 Created and ran some simple flows. While testing NIFI-13356 I found a new issue that wasn't covered in the ticket. The value parse can fail when coercing types of repeated fields. Since it's a new issue it shouldn't block the release. I'll create a ticket and fix this. Thanks for RMing David! Regards, Mark David Handermann ezt írta (időpont: 2024. júl. 1., H, 15:42): > +1 (binding) > > On Fri, Jun 28, 2024 at 8:40 AM David Handermann > wrote: > > > > Team, > > > > I am pleased to be calling this vote for the source release of Apache > > NiFi 2.0.0-M4. > > > > Please review the following guide for how to verify a release candidate > build: > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification > > > > The source being voted on the and the convenience binaries are > > available on the Apache Distribution Repository: > > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-2.0.0-M4 > > > > The build artifacts are available on the Apache Nexus Repository: > > > > https://repository.apache.org/content/repositories/orgapachenifi-1275 > > > > Git Tag: nifi-2.0.0-M4-RC1 > > Git Commit ID: 19c5be01d463bc38ec0f5008549a2a42e589436d > > GitHub Commit Link: > > > https://github.com/apache/nifi/commit/19c5be01d463bc38ec0f5008549a2a42e589436d > > > > Checksums of nifi-2.0.0-M4-source-release.zip > > > > SHA256: d882f05cec09ee1bfafaa3d4cde8f8660512d09765b5c400471f3a6e014029a6 > > SHA512: > d429cd67fb0b7d9737c59cb834106d7b6e25cbdb91e3ecc5290be865a1313cbebbc314c2e0e54228226f021c44f0a86c745a18c148247c632a739c871c5fa013 > > > > Release artifacts are signed with the following key: > > > > https://people.apache.org/keys/committer/exceptionfactory.asc > > > > KEYS file is available on the Apache Distribution Repository: > > > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > Issues resolved for this version: 153 > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354678 > > > > Release note highlights can be found on the project wiki: > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0-M4 > > > > 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. > > Then please vote: > > > > [] +1 Release this package as nifi-2.0.0-M4 > > [] +0 no opinion > > [] -1 Do not release this package because... >
Re: [VOTE] Release Apache NiFi 2.0.0-M4 (RC1)
+1 (binding) On Fri, Jun 28, 2024 at 8:40 AM David Handermann wrote: > > Team, > > I am pleased to be calling this vote for the source release of Apache > NiFi 2.0.0-M4. > > Please review the following guide for how to verify a release candidate build: > > https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification > > The source being voted on the and the convenience binaries are > available on the Apache Distribution Repository: > > https://dist.apache.org/repos/dist/dev/nifi/nifi-2.0.0-M4 > > The build artifacts are available on the Apache Nexus Repository: > > https://repository.apache.org/content/repositories/orgapachenifi-1275 > > Git Tag: nifi-2.0.0-M4-RC1 > Git Commit ID: 19c5be01d463bc38ec0f5008549a2a42e589436d > GitHub Commit Link: > https://github.com/apache/nifi/commit/19c5be01d463bc38ec0f5008549a2a42e589436d > > Checksums of nifi-2.0.0-M4-source-release.zip > > SHA256: d882f05cec09ee1bfafaa3d4cde8f8660512d09765b5c400471f3a6e014029a6 > SHA512: > d429cd67fb0b7d9737c59cb834106d7b6e25cbdb91e3ecc5290be865a1313cbebbc314c2e0e54228226f021c44f0a86c745a18c148247c632a739c871c5fa013 > > Release artifacts are signed with the following key: > > https://people.apache.org/keys/committer/exceptionfactory.asc > > KEYS file is available on the Apache Distribution Repository: > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > Issues resolved for this version: 153 > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354678 > > Release note highlights can be found on the project wiki: > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0-M4 > > 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. > Then please vote: > > [] +1 Release this package as nifi-2.0.0-M4 > [] +0 no opinion > [] -1 Do not release this package because...
Re: [VOTE] Release Apache NiFi 2.0.0-M4 (RC1)
+1 (binding) - Verified hashes and signatures - Successfully built NiFi 2.0.0-M4 with contrib-check in the following environment: - Ubuntu 22.04 6.5.0-41-generic - java version "21" 2023-09-19 LTS - Apache Maven 3.9.6 - Tested a simple flow using a python AI flowfiletransform processor - Verified NIFI-13427: Python API extended to support source processors - tested a flow with a source python processor - Tested S2S communication and HTTP data forwarding from MiNiFi C++ Thanks David for RMing! Best Regards, Gabor On Mon, 1 Jul 2024 at 10:41, Ferenc Kis wrote: > > +1 (non-binding) > > Went through the helper guide, local maven repo cleaned up, full clean > build with contrib check, verified signatures and hashes > > Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae) > Maven home: /Users/fkis/.sdkman/candidates/maven/current > Java version: 21.0.3, vendor: Azul Systems, Inc., runtime: > /Users/fkis/.sdkman/candidates/java/21.0.3-zulu/zulu-21.jdk/Contents/Home > Default locale: en_HU, platform encoding: UTF-8 > OS name: "mac os x", version: "14.5", arch: "aarch64", family: "mac" > > Validations performed: > - Started NiFi, created a simple flow with ListenHTTP and Input Port. > Validated ListenHTTP processor is able to receive data > - Started MiNiFi Java: > * created a simple GenerateFlowFile -> InvokeHttp flow and > GenerateFlowFile -> RemoteProcessGroup flow and pushed to MiNiFi via C2 > protocol > * Validated that connectivity between NiFi and MiNiFi works via both > InvokeHTTP and S2S > - NIFI-13395 Add python processors to MiNiFi: included Python processors > from the extension repo. Processors were included in the manifest > - NIFI-13396 Include python processors' allowable values in manifest: > values were correctly sent via the manifest > - NIFI-13242 Sync Resource command: synced (added and deleted) several > resources with C2 server - both asset and extension type > - NIFI-13450 Regenerate MiNiFi Agent Manifest between Heartbeats: manifest > is refreshed for each heartbeat correctly > - NIFI-13407 Sensible defaults for Manifest Id and Runtime Type in MiNiFi > bootstrap: parameters now got sensible values instead of empty string > > Thanks for RMing David! > > Regards > Ferenc > > On Sat, Jun 29, 2024 at 10:02 PM Csaba Bejan wrote: > > > +1 (binding) > > > >- Went through the helper guide and did a clean build > >- Verified signatures and hashes > >- Built on OSX 14.2.1 > >- Java version: Zulu21.28+85-CA (build 21+35) > >- Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546) > >- Started NiFi and created a simple flow, everything looks good > >- Started MiNiFi and verified integration with C2 Server. Played around > >with the C2 protocol > > > > Also verified: > > > >- NIFI-13407 Sensible defaults for Manifest Id and Runtime Type in > >MiNiFi bootstrap > >- NIFI-13450 Regenerate MiNiFi Agent Manifest between Heartbeats > >- It is not a release blocker just wanted to note that if c2 is enabled > > as manifest is regenerated for each HB at every HB I'm getting > > warnings > > which can be quite noisy > > 2024-06-29 15:37:34,920 WARN [pool-16-thread-1] > > o.a.n.m.StandardRuntimeManifestService There is no extension > > manifest for > > bundle [org.apache.nifi:python-extensions:unversioned] > > 2024-06-29 15:37:34,921 WARN [pool-16-thread-1] > > o.a.n.m.StandardRuntimeManifestService There is no extension > > manifest for > > bundle [default:system:unversioned] > >- NIFI-13436 Retain queue for non-modified connections during MiNiFi > >flow update > >- NIFI-13309 Lookup compatible bundles even if previous flow was empty > >- NIFI-13395 Add python processors to MiNiFi > > - Python processors are showing up under minifi now when enabled and > > dropped in the extension directory > > > > Thanks for RMing, David! > > > > Regards, > > > > Csaba > > > > On Sat, Jun 29, 2024 at 11:30 AM Joe Witt wrote: > > > > > +1 binding > > > > > > full clean build w contrib > > > full suite of integration tests including python/etc.. (see below) > > > built docker image and deployed over an existing set of volumes showing > > > upgrades well from previous releases > > > updated release notes a bit to focus more on end user perspective > > > > > > Test error during integration tests suggesting potentially
Re: [VOTE] Release Apache NiFi 2.0.0-M4 (RC1)
+1 (non-binding) Went through the helper guide, local maven repo cleaned up, full clean build with contrib check, verified signatures and hashes Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae) Maven home: /Users/fkis/.sdkman/candidates/maven/current Java version: 21.0.3, vendor: Azul Systems, Inc., runtime: /Users/fkis/.sdkman/candidates/java/21.0.3-zulu/zulu-21.jdk/Contents/Home Default locale: en_HU, platform encoding: UTF-8 OS name: "mac os x", version: "14.5", arch: "aarch64", family: "mac" Validations performed: - Started NiFi, created a simple flow with ListenHTTP and Input Port. Validated ListenHTTP processor is able to receive data - Started MiNiFi Java: * created a simple GenerateFlowFile -> InvokeHttp flow and GenerateFlowFile -> RemoteProcessGroup flow and pushed to MiNiFi via C2 protocol * Validated that connectivity between NiFi and MiNiFi works via both InvokeHTTP and S2S - NIFI-13395 Add python processors to MiNiFi: included Python processors from the extension repo. Processors were included in the manifest - NIFI-13396 Include python processors' allowable values in manifest: values were correctly sent via the manifest - NIFI-13242 Sync Resource command: synced (added and deleted) several resources with C2 server - both asset and extension type - NIFI-13450 Regenerate MiNiFi Agent Manifest between Heartbeats: manifest is refreshed for each heartbeat correctly - NIFI-13407 Sensible defaults for Manifest Id and Runtime Type in MiNiFi bootstrap: parameters now got sensible values instead of empty string Thanks for RMing David! Regards Ferenc On Sat, Jun 29, 2024 at 10:02 PM Csaba Bejan wrote: > +1 (binding) > >- Went through the helper guide and did a clean build >- Verified signatures and hashes >- Built on OSX 14.2.1 >- Java version: Zulu21.28+85-CA (build 21+35) >- Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546) >- Started NiFi and created a simple flow, everything looks good >- Started MiNiFi and verified integration with C2 Server. Played around >with the C2 protocol > > Also verified: > >- NIFI-13407 Sensible defaults for Manifest Id and Runtime Type in >MiNiFi bootstrap >- NIFI-13450 Regenerate MiNiFi Agent Manifest between Heartbeats >- It is not a release blocker just wanted to note that if c2 is enabled > as manifest is regenerated for each HB at every HB I'm getting > warnings > which can be quite noisy > 2024-06-29 15:37:34,920 WARN [pool-16-thread-1] > o.a.n.m.StandardRuntimeManifestService There is no extension > manifest for > bundle [org.apache.nifi:python-extensions:unversioned] > 2024-06-29 15:37:34,921 WARN [pool-16-thread-1] > o.a.n.m.StandardRuntimeManifestService There is no extension > manifest for > bundle [default:system:unversioned] >- NIFI-13436 Retain queue for non-modified connections during MiNiFi >flow update >- NIFI-13309 Lookup compatible bundles even if previous flow was empty >- NIFI-13395 Add python processors to MiNiFi > - Python processors are showing up under minifi now when enabled and > dropped in the extension directory > > Thanks for RMing, David! > > Regards, > > Csaba > > On Sat, Jun 29, 2024 at 11:30 AM Joe Witt wrote: > > > +1 binding > > > > full clean build w contrib > > full suite of integration tests including python/etc.. (see below) > > built docker image and deployed over an existing set of volumes showing > > upgrades well from previous releases > > updated release notes a bit to focus more on end user perspective > > > > Test error during integration tests suggesting potentially unstable test. > > Ran fine on second try > > [ERROR] Tests run: 33, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: > > 0.657 s <<< FAILURE! -- in > > org.apache.nifi.processors.standard.util.TestServerSFTPTransfer > > [ERROR] > > > > > org.apache.nifi.processors.standard.util.TestServerSFTPTransfer.testGetListingWithBatchSize > > -- Time elapsed: 0.019 s <<< ERROR! > > org.apache.nifi.processors.standard.socket.ClientConnectException: SSH > > Client connection failed [127.0.0.1:51893] > > at > > > > > org.apache.nifi.processors.standard.ssh.StandardSSHClientProvider.getClient(StandardSSHClientProvider.java:116) > > at > > > > > org.apache.nifi.processors.standard.util.SFTPTransfer.getSFTPClient(SFTPTransfer.java:631) > > at > > > > > org.apache.nifi.processors.standard.util.SFTPTransfer.getListing(SFTPTransfer.java:327) > > at > > > > > org.apache.nifi.processors.standard.util.SFT
Re: [VOTE] Release Apache NiFi 2.0.0-M4 (RC1)
+1 (binding) - Went through the helper guide and did a clean build - Verified signatures and hashes - Built on OSX 14.2.1 - Java version: Zulu21.28+85-CA (build 21+35) - Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546) - Started NiFi and created a simple flow, everything looks good - Started MiNiFi and verified integration with C2 Server. Played around with the C2 protocol Also verified: - NIFI-13407 Sensible defaults for Manifest Id and Runtime Type in MiNiFi bootstrap - NIFI-13450 Regenerate MiNiFi Agent Manifest between Heartbeats - It is not a release blocker just wanted to note that if c2 is enabled as manifest is regenerated for each HB at every HB I'm getting warnings which can be quite noisy 2024-06-29 15:37:34,920 WARN [pool-16-thread-1] o.a.n.m.StandardRuntimeManifestService There is no extension manifest for bundle [org.apache.nifi:python-extensions:unversioned] 2024-06-29 15:37:34,921 WARN [pool-16-thread-1] o.a.n.m.StandardRuntimeManifestService There is no extension manifest for bundle [default:system:unversioned] - NIFI-13436 Retain queue for non-modified connections during MiNiFi flow update - NIFI-13309 Lookup compatible bundles even if previous flow was empty - NIFI-13395 Add python processors to MiNiFi - Python processors are showing up under minifi now when enabled and dropped in the extension directory Thanks for RMing, David! Regards, Csaba On Sat, Jun 29, 2024 at 11:30 AM Joe Witt wrote: > +1 binding > > full clean build w contrib > full suite of integration tests including python/etc.. (see below) > built docker image and deployed over an existing set of volumes showing > upgrades well from previous releases > updated release notes a bit to focus more on end user perspective > > Test error during integration tests suggesting potentially unstable test. > Ran fine on second try > [ERROR] Tests run: 33, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: > 0.657 s <<< FAILURE! -- in > org.apache.nifi.processors.standard.util.TestServerSFTPTransfer > [ERROR] > > org.apache.nifi.processors.standard.util.TestServerSFTPTransfer.testGetListingWithBatchSize > -- Time elapsed: 0.019 s <<< ERROR! > org.apache.nifi.processors.standard.socket.ClientConnectException: SSH > Client connection failed [127.0.0.1:51893] > at > > org.apache.nifi.processors.standard.ssh.StandardSSHClientProvider.getClient(StandardSSHClientProvider.java:116) > at > > org.apache.nifi.processors.standard.util.SFTPTransfer.getSFTPClient(SFTPTransfer.java:631) > at > > org.apache.nifi.processors.standard.util.SFTPTransfer.getListing(SFTPTransfer.java:327) > at > > org.apache.nifi.processors.standard.util.SFTPTransfer.getListing(SFTPTransfer.java:289) > at > > org.apache.nifi.processors.standard.util.TestServerSFTPTransfer.testGetListingWithBatchSize(TestServerSFTPTransfer.java:225) > at java.base/java.lang.reflect.Method.invoke(Method.java:580) > at java.base/java.util.ArrayList.forEach(ArrayList.java:1596) > at java.base/java.util.ArrayList.forEach(ArrayList.java:1596) > Caused by: net.schmizz.sshj.transport.TransportException: Timeout expired: > 3 MILLISECONDS > at > > net.schmizz.sshj.transport.TransportException$1.chain(TransportException.java:33) > at > > net.schmizz.sshj.transport.TransportException$1.chain(TransportException.java:27) > at net.schmizz.concurrent.Promise.retrieve(Promise.java:139) > at net.schmizz.concurrent.Event.await(Event.java:105) > at > net.schmizz.sshj.transport.KeyExchanger.waitForDone(KeyExchanger.java:172) > at net.schmizz.sshj.transport.KeyExchanger.startKex(KeyExchanger.java:160) > at net.schmizz.sshj.transport.TransportImpl.doKex(TransportImpl.java:254) > at net.schmizz.sshj.SSHClient.doKex(SSHClient.java:824) > at net.schmizz.sshj.SSHClient.onConnect(SSHClient.java:812) > at net.schmizz.sshj.SocketClient.connect(SocketClient.java:69) > at > > org.apache.nifi.processors.standard.ssh.StandardSSHClientProvider.getClient(StandardSSHClientProvider.java:113) > ... 7 more > Caused by: java.util.concurrent.TimeoutException: Timeout expired: 3 > MILLISECONDS > ... 16 more > > On Sat, Jun 29, 2024 at 7:01 AM Pierre Villard < > pierre.villard...@gmail.com> > wrote: > > > +1, binding > > > > Went through the usual steps, deployed a 3-nodes secured cluster in GCP > > with NiFi Registry and confirmed everything is working as expected. > > > > Thanks for taking care of this release David! > > > > Pierre > > > > Le ven. 28 juin 2024 à 22:22, Dan S a écrit : > > > > > +1 (non-binding) > > > Ran through Release Candidate Verification > > > Verified signatur
Re: [VOTE] Release Apache NiFi 2.0.0-M4 (RC1)
+1 binding full clean build w contrib full suite of integration tests including python/etc.. (see below) built docker image and deployed over an existing set of volumes showing upgrades well from previous releases updated release notes a bit to focus more on end user perspective Test error during integration tests suggesting potentially unstable test. Ran fine on second try [ERROR] Tests run: 33, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.657 s <<< FAILURE! -- in org.apache.nifi.processors.standard.util.TestServerSFTPTransfer [ERROR] org.apache.nifi.processors.standard.util.TestServerSFTPTransfer.testGetListingWithBatchSize -- Time elapsed: 0.019 s <<< ERROR! org.apache.nifi.processors.standard.socket.ClientConnectException: SSH Client connection failed [127.0.0.1:51893] at org.apache.nifi.processors.standard.ssh.StandardSSHClientProvider.getClient(StandardSSHClientProvider.java:116) at org.apache.nifi.processors.standard.util.SFTPTransfer.getSFTPClient(SFTPTransfer.java:631) at org.apache.nifi.processors.standard.util.SFTPTransfer.getListing(SFTPTransfer.java:327) at org.apache.nifi.processors.standard.util.SFTPTransfer.getListing(SFTPTransfer.java:289) at org.apache.nifi.processors.standard.util.TestServerSFTPTransfer.testGetListingWithBatchSize(TestServerSFTPTransfer.java:225) at java.base/java.lang.reflect.Method.invoke(Method.java:580) at java.base/java.util.ArrayList.forEach(ArrayList.java:1596) at java.base/java.util.ArrayList.forEach(ArrayList.java:1596) Caused by: net.schmizz.sshj.transport.TransportException: Timeout expired: 3 MILLISECONDS at net.schmizz.sshj.transport.TransportException$1.chain(TransportException.java:33) at net.schmizz.sshj.transport.TransportException$1.chain(TransportException.java:27) at net.schmizz.concurrent.Promise.retrieve(Promise.java:139) at net.schmizz.concurrent.Event.await(Event.java:105) at net.schmizz.sshj.transport.KeyExchanger.waitForDone(KeyExchanger.java:172) at net.schmizz.sshj.transport.KeyExchanger.startKex(KeyExchanger.java:160) at net.schmizz.sshj.transport.TransportImpl.doKex(TransportImpl.java:254) at net.schmizz.sshj.SSHClient.doKex(SSHClient.java:824) at net.schmizz.sshj.SSHClient.onConnect(SSHClient.java:812) at net.schmizz.sshj.SocketClient.connect(SocketClient.java:69) at org.apache.nifi.processors.standard.ssh.StandardSSHClientProvider.getClient(StandardSSHClientProvider.java:113) ... 7 more Caused by: java.util.concurrent.TimeoutException: Timeout expired: 3 MILLISECONDS ... 16 more On Sat, Jun 29, 2024 at 7:01 AM Pierre Villard wrote: > +1, binding > > Went through the usual steps, deployed a 3-nodes secured cluster in GCP > with NiFi Registry and confirmed everything is working as expected. > > Thanks for taking care of this release David! > > Pierre > > Le ven. 28 juin 2024 à 22:22, Dan S a écrit : > > > +1 (non-binding) > > Ran through Release Candidate Verification > > Verified signatures and hashes > > Built with: > > > > Maven home: /opt/apache-maven-3.9.6 > > Java version: 21.0.3, vendor: Red Hat, Inc., runtime: > > /usr/lib/jvm/java-21-openjdk-21.0.3.0.9-1.el8.x86_64 > > Default locale: en_US, platform encoding: UTF-8 > > OS name: "linux", version: "4.18.0-513.24.1.el8_9.x86_64", arch: "amd64", > > family: "unix" > > > > Exercised new feature NIFI-13304 SplitExcel > > Discovered bug NIFI-13466 > > <https://issues.apache.org/jira/browse/NIFI-13466> and > > created task to research NIFI-13467 > > <https://issues.apache.org/jira/browse/NIFI-13467> > > > > Thanks for RM'ing David and all your hard work to get to this point! > > > > On Fri, Jun 28, 2024 at 1:16 PM Matt Burgess > wrote: > > > > > +1 (binding) Ran through release helper and tried various flows, > verified > > > versioning against a NiFi Registry (not the Git-backed one) > > > > > > Apache Maven 3.9.7 (8b094c9513efc1b9ce2d952b3b9c8eaedaf8cbf0) > > > Java version: 21, vendor: Oracle Corporation, runtime: > > > /Users/mburgess/.sdkman/candidates/java/21-oracle > > > Default locale: en_US, platform encoding: UTF-8 > > > OS name: "mac os x", version: "14.5", arch: "aarch64", family: "mac" > > > > > > Thanks for RM'ing David! > > > > > > On Fri, Jun 28, 2024 at 9:40 AM David Handermann < > > > exceptionfact...@apache.org> wrote: > > > > > > > Team, > > > > > > > > I am pleased to be calling this vote for the source release of Apache > > > > NiFi 2.0.0-M4. > > > > > > > > Please review the following guide for how to verify a release > candidate > > > > bu
Re: [VOTE] Release Apache NiFi 2.0.0-M4 (RC1)
+1, binding Went through the usual steps, deployed a 3-nodes secured cluster in GCP with NiFi Registry and confirmed everything is working as expected. Thanks for taking care of this release David! Pierre Le ven. 28 juin 2024 à 22:22, Dan S a écrit : > +1 (non-binding) > Ran through Release Candidate Verification > Verified signatures and hashes > Built with: > > Maven home: /opt/apache-maven-3.9.6 > Java version: 21.0.3, vendor: Red Hat, Inc., runtime: > /usr/lib/jvm/java-21-openjdk-21.0.3.0.9-1.el8.x86_64 > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "4.18.0-513.24.1.el8_9.x86_64", arch: "amd64", > family: "unix" > > Exercised new feature NIFI-13304 SplitExcel > Discovered bug NIFI-13466 > <https://issues.apache.org/jira/browse/NIFI-13466> and > created task to research NIFI-13467 > <https://issues.apache.org/jira/browse/NIFI-13467> > > Thanks for RM'ing David and all your hard work to get to this point! > > On Fri, Jun 28, 2024 at 1:16 PM Matt Burgess wrote: > > > +1 (binding) Ran through release helper and tried various flows, verified > > versioning against a NiFi Registry (not the Git-backed one) > > > > Apache Maven 3.9.7 (8b094c9513efc1b9ce2d952b3b9c8eaedaf8cbf0) > > Java version: 21, vendor: Oracle Corporation, runtime: > > /Users/mburgess/.sdkman/candidates/java/21-oracle > > Default locale: en_US, platform encoding: UTF-8 > > OS name: "mac os x", version: "14.5", arch: "aarch64", family: "mac" > > > > Thanks for RM'ing David! > > > > On Fri, Jun 28, 2024 at 9:40 AM David Handermann < > > exceptionfact...@apache.org> wrote: > > > > > Team, > > > > > > I am pleased to be calling this vote for the source release of Apache > > > NiFi 2.0.0-M4. > > > > > > Please review the following guide for how to verify a release candidate > > > build: > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification > > > > > > The source being voted on the and the convenience binaries are > > > available on the Apache Distribution Repository: > > > > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-2.0.0-M4 > > > > > > The build artifacts are available on the Apache Nexus Repository: > > > > > > https://repository.apache.org/content/repositories/orgapachenifi-1275 > > > > > > Git Tag: nifi-2.0.0-M4-RC1 > > > Git Commit ID: 19c5be01d463bc38ec0f5008549a2a42e589436d > > > GitHub Commit Link: > > > > > > > > > https://github.com/apache/nifi/commit/19c5be01d463bc38ec0f5008549a2a42e589436d > > > > > > Checksums of nifi-2.0.0-M4-source-release.zip > > > > > > SHA256: > d882f05cec09ee1bfafaa3d4cde8f8660512d09765b5c400471f3a6e014029a6 > > > SHA512: > > > > > > d429cd67fb0b7d9737c59cb834106d7b6e25cbdb91e3ecc5290be865a1313cbebbc314c2e0e54228226f021c44f0a86c745a18c148247c632a739c871c5fa013 > > > > > > Release artifacts are signed with the following key: > > > > > > https://people.apache.org/keys/committer/exceptionfactory.asc > > > > > > KEYS file is available on the Apache Distribution Repository: > > > > > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > > > Issues resolved for this version: 153 > > > > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354678 > > > > > > Release note highlights can be found on the project wiki: > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0-M4 > > > > > > 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. > > > Then please vote: > > > > > > [] +1 Release this package as nifi-2.0.0-M4 > > > [] +0 no opinion > > > [] -1 Do not release this package because... > > > > > >
Re: [VOTE] Release Apache NiFi 2.0.0-M4 (RC1)
+1 (non-binding) Ran through Release Candidate Verification Verified signatures and hashes Built with: Maven home: /opt/apache-maven-3.9.6 Java version: 21.0.3, vendor: Red Hat, Inc., runtime: /usr/lib/jvm/java-21-openjdk-21.0.3.0.9-1.el8.x86_64 Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "4.18.0-513.24.1.el8_9.x86_64", arch: "amd64", family: "unix" Exercised new feature NIFI-13304 SplitExcel Discovered bug NIFI-13466 <https://issues.apache.org/jira/browse/NIFI-13466> and created task to research NIFI-13467 <https://issues.apache.org/jira/browse/NIFI-13467> Thanks for RM'ing David and all your hard work to get to this point! On Fri, Jun 28, 2024 at 1:16 PM Matt Burgess wrote: > +1 (binding) Ran through release helper and tried various flows, verified > versioning against a NiFi Registry (not the Git-backed one) > > Apache Maven 3.9.7 (8b094c9513efc1b9ce2d952b3b9c8eaedaf8cbf0) > Java version: 21, vendor: Oracle Corporation, runtime: > /Users/mburgess/.sdkman/candidates/java/21-oracle > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "14.5", arch: "aarch64", family: "mac" > > Thanks for RM'ing David! > > On Fri, Jun 28, 2024 at 9:40 AM David Handermann < > exceptionfact...@apache.org> wrote: > > > Team, > > > > I am pleased to be calling this vote for the source release of Apache > > NiFi 2.0.0-M4. > > > > Please review the following guide for how to verify a release candidate > > build: > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification > > > > The source being voted on the and the convenience binaries are > > available on the Apache Distribution Repository: > > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-2.0.0-M4 > > > > The build artifacts are available on the Apache Nexus Repository: > > > > https://repository.apache.org/content/repositories/orgapachenifi-1275 > > > > Git Tag: nifi-2.0.0-M4-RC1 > > Git Commit ID: 19c5be01d463bc38ec0f5008549a2a42e589436d > > GitHub Commit Link: > > > > > https://github.com/apache/nifi/commit/19c5be01d463bc38ec0f5008549a2a42e589436d > > > > Checksums of nifi-2.0.0-M4-source-release.zip > > > > SHA256: d882f05cec09ee1bfafaa3d4cde8f8660512d09765b5c400471f3a6e014029a6 > > SHA512: > > > d429cd67fb0b7d9737c59cb834106d7b6e25cbdb91e3ecc5290be865a1313cbebbc314c2e0e54228226f021c44f0a86c745a18c148247c632a739c871c5fa013 > > > > Release artifacts are signed with the following key: > > > > https://people.apache.org/keys/committer/exceptionfactory.asc > > > > KEYS file is available on the Apache Distribution Repository: > > > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > Issues resolved for this version: 153 > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354678 > > > > Release note highlights can be found on the project wiki: > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0-M4 > > > > 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. > > Then please vote: > > > > [] +1 Release this package as nifi-2.0.0-M4 > > [] +0 no opinion > > [] -1 Do not release this package because... > > >
Re: [VOTE] Release Apache NiFi 2.0.0-M4 (RC1)
+1 (non-binding) checksums look good Compiled withApache Maven 3.9.8 Java 21.0.3 (openjdk) RHEL 8 Set up/ran site-to-site flow and some rest api calls Thank you David and team, Nissim Shiman On Friday, June 28, 2024 at 09:40:57 AM EDT, David Handermann wrote: Team, I am pleased to be calling this vote for the source release of Apache NiFi 2.0.0-M4. Please review the following guide for how to verify a release candidate build: https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification The source being voted on the and the convenience binaries are available on the Apache Distribution Repository: https://dist.apache.org/repos/dist/dev/nifi/nifi-2.0.0-M4 The build artifacts are available on the Apache Nexus Repository: https://repository.apache.org/content/repositories/orgapachenifi-1275 Git Tag: nifi-2.0.0-M4-RC1 Git Commit ID: 19c5be01d463bc38ec0f5008549a2a42e589436d GitHub Commit Link: https://github.com/apache/nifi/commit/19c5be01d463bc38ec0f5008549a2a42e589436d Checksums of nifi-2.0.0-M4-source-release.zip SHA256: d882f05cec09ee1bfafaa3d4cde8f8660512d09765b5c400471f3a6e014029a6 SHA512: d429cd67fb0b7d9737c59cb834106d7b6e25cbdb91e3ecc5290be865a1313cbebbc314c2e0e54228226f021c44f0a86c745a18c148247c632a739c871c5fa013 Release artifacts are signed with the following key: https://people.apache.org/keys/committer/exceptionfactory.asc KEYS file is available on the Apache Distribution Repository: https://dist.apache.org/repos/dist/release/nifi/KEYS Issues resolved for this version: 153 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354678 Release note highlights can be found on the project wiki: https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0-M4 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. Then please vote: [] +1 Release this package as nifi-2.0.0-M4 [] +0 no opinion [] -1 Do not release this package because...
Re: [VOTE] Release Apache NiFi 2.0.0-M4 (RC1)
+1 (binding) Ran through release helper and tried various flows, verified versioning against a NiFi Registry (not the Git-backed one) Apache Maven 3.9.7 (8b094c9513efc1b9ce2d952b3b9c8eaedaf8cbf0) Java version: 21, vendor: Oracle Corporation, runtime: /Users/mburgess/.sdkman/candidates/java/21-oracle Default locale: en_US, platform encoding: UTF-8 OS name: "mac os x", version: "14.5", arch: "aarch64", family: "mac" Thanks for RM'ing David! On Fri, Jun 28, 2024 at 9:40 AM David Handermann < exceptionfact...@apache.org> wrote: > Team, > > I am pleased to be calling this vote for the source release of Apache > NiFi 2.0.0-M4. > > Please review the following guide for how to verify a release candidate > build: > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification > > The source being voted on the and the convenience binaries are > available on the Apache Distribution Repository: > > https://dist.apache.org/repos/dist/dev/nifi/nifi-2.0.0-M4 > > The build artifacts are available on the Apache Nexus Repository: > > https://repository.apache.org/content/repositories/orgapachenifi-1275 > > Git Tag: nifi-2.0.0-M4-RC1 > Git Commit ID: 19c5be01d463bc38ec0f5008549a2a42e589436d > GitHub Commit Link: > > https://github.com/apache/nifi/commit/19c5be01d463bc38ec0f5008549a2a42e589436d > > Checksums of nifi-2.0.0-M4-source-release.zip > > SHA256: d882f05cec09ee1bfafaa3d4cde8f8660512d09765b5c400471f3a6e014029a6 > SHA512: > d429cd67fb0b7d9737c59cb834106d7b6e25cbdb91e3ecc5290be865a1313cbebbc314c2e0e54228226f021c44f0a86c745a18c148247c632a739c871c5fa013 > > Release artifacts are signed with the following key: > > https://people.apache.org/keys/committer/exceptionfactory.asc > > KEYS file is available on the Apache Distribution Repository: > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > Issues resolved for this version: 153 > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354678 > > Release note highlights can be found on the project wiki: > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0-M4 > > 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. > Then please vote: > > [] +1 Release this package as nifi-2.0.0-M4 > [] +0 no opinion > [] -1 Do not release this package because... >
Re: [VOTE] Release Apache NiFi 1.27.0 (RC1)
-1, binding I have the same error, thanks for flagging Nassim. I'm cancelling the vote for the RC1 and will start a RC2 once we fix the issue. Le ven. 28 juin 2024 à 17:10, Nissim Shiman a écrit : > Team, > > I am running into difficulty starting nifi registry. > It was compiled (and is being run) with java 1.8 (openjdk-1.8.0.412) > on RHEL 8 > > nifi itself compiles and runs fine. > > > I was wondering is other people have run into anything similar. > > > The error is (from nifi-registry-app.log): > 2024-06-28 14:44:33,150 WARN [main] d.o.a.n.r.bootstrap.RunNiFiRegistry > Support for Java 8 is deprecated. Java 11 is the minimum recommended > versionorg.apache.nifi.deprecation.log.DeprecationException: Reference > Class [org.apache.nifi.registry.bootstrap.RunNiFiRegistry] ClassLoader > [sun.misc.Launcher$AppClassLoader@232204a1] at > org.apache.nifi.deprecation.log.StandardDeprecationLogger.getExtendedArguments(StandardDeprecationLogger.java:63) > at > org.apache.nifi.deprecation.log.StandardDeprecationLogger.warn(StandardDeprecationLogger.java:54) > at > org.apache.nifi.registry.bootstrap.RunNiFiRegistry.start(RunNiFiRegistry.java:941) > at > org.apache.nifi.registry.bootstrap.RunNiFiRegistry.main(RunNiFiRegistry.java:206)2024-06-28 > 14:44:33,506 INFO [main] org.apache.nifi.registry.NiFiRegistry Launching > NiFi Registry...2024-06-28 14:44:33,508 INFO [main] > org.apache.nifi.registry.NiFiRegistry Read property protection key from > /registry_1_27_0_RC1/nifi-registry-1.27.0/conf/bootstrap.conf2024-06-28 > 14:44:33,525 WARN [main] o.a.n.p.AbstractBootstrapPropertiesLoader > No encryption key present in the bootstrap.conf file at > /registry_1_27_0_RC1/nifi-registry-1.27.0/conf/bootstrap.conf > > > and (nifi-registry-bootstrap.log) > > 2024-06-28 14:44:34,477 ERROR [NiFi logging handler] > org.apache.nifi.registry.StdErr Exception in thread "main" > java.lang.NoClassDefFoundError: > org/apache/nifi/deprecation/log/DeprecationLoggerFactory2024-06-28 > 14:44:34,477 ERROR [NiFi logging handler] org.apache.nifi.registry.StdErr > at > org.apache.nifi.registry.properties.NiFiRegistryPropertiesLoader.(NiFiRegistryPropertiesLoader.java:38)2024-06-28 > 14:44:34,477 ERROR [NiFi logging handler] org.apache.nifi.registry.StdErr > at java.lang.Class.forName0(Native Method)2024-06-28 14:44:34,477 ERROR > [NiFi logging handler] org.apache.nifi.registry.StdErr at > java.lang.Class.forName(Class.java:348)2024-06-28 14:44:34,477 ERROR [NiFi > logging handler] org.apache.nifi.registry.StdErr at > org.apache.nifi.registry.NiFiRegistry.initializeProperties(NiFiRegistry.java:189)2024-06-28 > 14:44:34,477 ERROR [NiFi logging handler] org.apache.nifi.registry.StdErr > at > org.apache.nifi.registry.NiFiRegistry.main(NiFiRegistry.java:153)2024-06-28 > 14:44:34,477 ERROR [NiFi logging handler] org.apache.nifi.registry.StdErr > Caused by: java.lang.ClassNotFoundException: > org.apache.nifi.deprecation.log.DeprecationLoggerFactory2024-06-28 > 14:44:34,477 ERROR [NiFi logging handler] org.apache.nifi.registry.StdErr > at java.net.URLClassLoader.findClass(URLClassLoader.java:387)2024-06-28 > 14:44:34,477 ERROR [NiFi logging handler] org.apache.nifi.registry.StdErr > at java.lang.ClassLoader.loadClass(ClassLoader.java:418)2024-06-28 > 14:44:34,477 ERROR [NiFi logging handler] org.apache.nifi.registry.StdErr > at java.lang.ClassLoader.loadClass(ClassLoader.java:351)2024-06-28 > 14:44:34,477 ERROR [NiFi logging handler] org.apache.nifi.registry.StdErr > ... 5 more2024-06-28 14:44:35,174 INFO [main] > o.a.n.registry.bootstrap.RunNiFiRegistry NiFi Registry never started. Will > not restart NiFi Registry > > > Thanks, > Nissim Shiman > On Thursday, June 27, 2024 at 09:01:30 PM UTC, Pierre Villard < > pierre.villard...@gmail.com> wrote: > > Team, > > I am pleased to be calling this vote for the source release of Apache NiFi > 1.27.0. > > Please review the following guide for how to verify a release candidate > build: > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification > > The source being voted on the and the convenience binaries are available on > the Apache Distribution Repository: > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.27.0 > > The build artifacts are available on the Apache Nexus Repository: > > https://repository.apache.org/content/repositories/orgapachenifi-1272 > > Git Tag: nifi-1.27.0-RC1 > Git Commit ID: bd86d1f07fe8d0f45b72e91e925ee85ffa7ed143 > GitHub Commit Link: > > https://github.com/apache/nifi/commit/bd86d1f07fe8d0f45b72e91e925ee85ffa7ed143 > > Checksums of nifi-1.27.0-source-release.zip > > SHA256: 7df2933b366aff8e1dc3abe9bafb3e8891186ca937d3
Re: [VOTE] Release Apache NiFi 1.27.0 (RC1)
Team, I am running into difficulty starting nifi registry. It was compiled (and is being run) with java 1.8 (openjdk-1.8.0.412) on RHEL 8 nifi itself compiles and runs fine. I was wondering is other people have run into anything similar. The error is (from nifi-registry-app.log): 2024-06-28 14:44:33,150 WARN [main] d.o.a.n.r.bootstrap.RunNiFiRegistry Support for Java 8 is deprecated. Java 11 is the minimum recommended versionorg.apache.nifi.deprecation.log.DeprecationException: Reference Class [org.apache.nifi.registry.bootstrap.RunNiFiRegistry] ClassLoader [sun.misc.Launcher$AppClassLoader@232204a1] at org.apache.nifi.deprecation.log.StandardDeprecationLogger.getExtendedArguments(StandardDeprecationLogger.java:63) at org.apache.nifi.deprecation.log.StandardDeprecationLogger.warn(StandardDeprecationLogger.java:54) at org.apache.nifi.registry.bootstrap.RunNiFiRegistry.start(RunNiFiRegistry.java:941) at org.apache.nifi.registry.bootstrap.RunNiFiRegistry.main(RunNiFiRegistry.java:206)2024-06-28 14:44:33,506 INFO [main] org.apache.nifi.registry.NiFiRegistry Launching NiFi Registry...2024-06-28 14:44:33,508 INFO [main] org.apache.nifi.registry.NiFiRegistry Read property protection key from /registry_1_27_0_RC1/nifi-registry-1.27.0/conf/bootstrap.conf2024-06-28 14:44:33,525 WARN [main] o.a.n.p.AbstractBootstrapPropertiesLoader No encryption key present in the bootstrap.conf file at /registry_1_27_0_RC1/nifi-registry-1.27.0/conf/bootstrap.conf and (nifi-registry-bootstrap.log) 2024-06-28 14:44:34,477 ERROR [NiFi logging handler] org.apache.nifi.registry.StdErr Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/nifi/deprecation/log/DeprecationLoggerFactory2024-06-28 14:44:34,477 ERROR [NiFi logging handler] org.apache.nifi.registry.StdErr at org.apache.nifi.registry.properties.NiFiRegistryPropertiesLoader.(NiFiRegistryPropertiesLoader.java:38)2024-06-28 14:44:34,477 ERROR [NiFi logging handler] org.apache.nifi.registry.StdErr at java.lang.Class.forName0(Native Method)2024-06-28 14:44:34,477 ERROR [NiFi logging handler] org.apache.nifi.registry.StdErr at java.lang.Class.forName(Class.java:348)2024-06-28 14:44:34,477 ERROR [NiFi logging handler] org.apache.nifi.registry.StdErr at org.apache.nifi.registry.NiFiRegistry.initializeProperties(NiFiRegistry.java:189)2024-06-28 14:44:34,477 ERROR [NiFi logging handler] org.apache.nifi.registry.StdErr at org.apache.nifi.registry.NiFiRegistry.main(NiFiRegistry.java:153)2024-06-28 14:44:34,477 ERROR [NiFi logging handler] org.apache.nifi.registry.StdErr Caused by: java.lang.ClassNotFoundException: org.apache.nifi.deprecation.log.DeprecationLoggerFactory2024-06-28 14:44:34,477 ERROR [NiFi logging handler] org.apache.nifi.registry.StdErr at java.net.URLClassLoader.findClass(URLClassLoader.java:387)2024-06-28 14:44:34,477 ERROR [NiFi logging handler] org.apache.nifi.registry.StdErr at java.lang.ClassLoader.loadClass(ClassLoader.java:418)2024-06-28 14:44:34,477 ERROR [NiFi logging handler] org.apache.nifi.registry.StdErr at java.lang.ClassLoader.loadClass(ClassLoader.java:351)2024-06-28 14:44:34,477 ERROR [NiFi logging handler] org.apache.nifi.registry.StdErr ... 5 more2024-06-28 14:44:35,174 INFO [main] o.a.n.registry.bootstrap.RunNiFiRegistry NiFi Registry never started. Will not restart NiFi Registry Thanks, Nissim Shiman On Thursday, June 27, 2024 at 09:01:30 PM UTC, Pierre Villard wrote: Team, I am pleased to be calling this vote for the source release of Apache NiFi 1.27.0. Please review the following guide for how to verify a release candidate build: https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification The source being voted on the and the convenience binaries are available on the Apache Distribution Repository: https://dist.apache.org/repos/dist/dev/nifi/nifi-1.27.0 The build artifacts are available on the Apache Nexus Repository: https://repository.apache.org/content/repositories/orgapachenifi-1272 Git Tag: nifi-1.27.0-RC1 Git Commit ID: bd86d1f07fe8d0f45b72e91e925ee85ffa7ed143 GitHub Commit Link: https://github.com/apache/nifi/commit/bd86d1f07fe8d0f45b72e91e925ee85ffa7ed143 Checksums of nifi-1.27.0-source-release.zip SHA256: 7df2933b366aff8e1dc3abe9bafb3e8891186ca937d34d646952d43db624d4e2 SHA512: 36c0f107b5a98388c2fb2c48d24f4df9980d9685a9b31d08c0a7a6a47b54de556ff368a8c622a5011dab4448274fc16f6e18c5d29368a81d003baa7c7382bd4d Release artifacts are signed with the following key: https://people.apache.org/keys/committer/pvillard.asc KEYS file is available on the Apache Distribution Repository: https://dist.apache.org/repos/dist/release/nifi/KEYS Issues resolved for this version: 35 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354832 Release note highlights can be found on the project wiki: https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.27.0 The vote wi
[VOTE] Release Apache NiFi 2.0.0-M4 (RC1)
Team, I am pleased to be calling this vote for the source release of Apache NiFi 2.0.0-M4. Please review the following guide for how to verify a release candidate build: https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification The source being voted on the and the convenience binaries are available on the Apache Distribution Repository: https://dist.apache.org/repos/dist/dev/nifi/nifi-2.0.0-M4 The build artifacts are available on the Apache Nexus Repository: https://repository.apache.org/content/repositories/orgapachenifi-1275 Git Tag: nifi-2.0.0-M4-RC1 Git Commit ID: 19c5be01d463bc38ec0f5008549a2a42e589436d GitHub Commit Link: https://github.com/apache/nifi/commit/19c5be01d463bc38ec0f5008549a2a42e589436d Checksums of nifi-2.0.0-M4-source-release.zip SHA256: d882f05cec09ee1bfafaa3d4cde8f8660512d09765b5c400471f3a6e014029a6 SHA512: d429cd67fb0b7d9737c59cb834106d7b6e25cbdb91e3ecc5290be865a1313cbebbc314c2e0e54228226f021c44f0a86c745a18c148247c632a739c871c5fa013 Release artifacts are signed with the following key: https://people.apache.org/keys/committer/exceptionfactory.asc KEYS file is available on the Apache Distribution Repository: https://dist.apache.org/repos/dist/release/nifi/KEYS Issues resolved for this version: 153 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354678 Release note highlights can be found on the project wiki: https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0-M4 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. Then please vote: [] +1 Release this package as nifi-2.0.0-M4 [] +0 no opinion [] -1 Do not release this package because...
Re: [VOTE] Release Apache NiFi 1.27.0 (RC1)
fwiw, I also dry-ran our mirroring script [1] which looks at checksums as well and it was happy with everything (it looks at sha256, sha512 and asc). Hashes also match what is in this mail thread. [1] https://github.com/stackabletech/docker-images/blob/main/nifi/upload_new_nifi_version.sh On Fri, Jun 28, 2024 at 10:52 AM Pierre Villard wrote: > Hi Matt, > > I extended my key weeks ago but for some reason the ASF has not synced the > extended key. I'll try to get this fixed asap. > Using my fingerprint, you can find my extended key on well known key > servers. > > I checked the checksums again and it seems to be ok on my side. > > Sorry for the inconvenience, > Pierre > > Le ven. 28 juin 2024 à 00:15, Matt Burgess a écrit > : > > > I'm seeing SHA256 and SHA512 mismatches, also my automated RC script > > noticed your GPG key is expired. > > > > On Thu, Jun 27, 2024 at 5:11 PM Pierre Villard < > > pierre.villard...@gmail.com> > > wrote: > > > > > Team, > > > > > > I am pleased to be calling this vote for the source release of Apache > > NiFi > > > 1.27.0. > > > > > > Please review the following guide for how to verify a release candidate > > > build: > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification > > > > > > The source being voted on the and the convenience binaries are > available > > on > > > the Apache Distribution Repository: > > > > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.27.0 > > > > > > The build artifacts are available on the Apache Nexus Repository: > > > > > > https://repository.apache.org/content/repositories/orgapachenifi-1272 > > > > > > Git Tag: nifi-1.27.0-RC1 > > > Git Commit ID: bd86d1f07fe8d0f45b72e91e925ee85ffa7ed143 > > > GitHub Commit Link: > > > > > > > > > https://github.com/apache/nifi/commit/bd86d1f07fe8d0f45b72e91e925ee85ffa7ed143 > > > > > > Checksums of nifi-1.27.0-source-release.zip > > > > > > SHA256: > 7df2933b366aff8e1dc3abe9bafb3e8891186ca937d34d646952d43db624d4e2 > > > SHA512: > > > > > > > > > 36c0f107b5a98388c2fb2c48d24f4df9980d9685a9b31d08c0a7a6a47b54de556ff368a8c622a5011dab4448274fc16f6e18c5d29368a81d003baa7c7382bd4d > > > > > > Release artifacts are signed with the following key: > > > > > > https://people.apache.org/keys/committer/pvillard.asc > > > > > > KEYS file is available on the Apache Distribution Repository: > > > > > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > > > Issues resolved for this version: 35 > > > > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354832 > > > > > > Release note highlights can be found on the project wiki: > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.27.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. > Then > > > please vote: > > > > > > [] +1 Release this package as nifi-1.27.0 > > > [] +0 no opinion > > > [] -1 Do not release this package because... > > > > > >
Re: [VOTE] Release Apache NiFi 1.27.0 (RC1)
Hi Matt, I extended my key weeks ago but for some reason the ASF has not synced the extended key. I'll try to get this fixed asap. Using my fingerprint, you can find my extended key on well known key servers. I checked the checksums again and it seems to be ok on my side. Sorry for the inconvenience, Pierre Le ven. 28 juin 2024 à 00:15, Matt Burgess a écrit : > I'm seeing SHA256 and SHA512 mismatches, also my automated RC script > noticed your GPG key is expired. > > On Thu, Jun 27, 2024 at 5:11 PM Pierre Villard < > pierre.villard...@gmail.com> > wrote: > > > Team, > > > > I am pleased to be calling this vote for the source release of Apache > NiFi > > 1.27.0. > > > > Please review the following guide for how to verify a release candidate > > build: > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification > > > > The source being voted on the and the convenience binaries are available > on > > the Apache Distribution Repository: > > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.27.0 > > > > The build artifacts are available on the Apache Nexus Repository: > > > > https://repository.apache.org/content/repositories/orgapachenifi-1272 > > > > Git Tag: nifi-1.27.0-RC1 > > Git Commit ID: bd86d1f07fe8d0f45b72e91e925ee85ffa7ed143 > > GitHub Commit Link: > > > > > https://github.com/apache/nifi/commit/bd86d1f07fe8d0f45b72e91e925ee85ffa7ed143 > > > > Checksums of nifi-1.27.0-source-release.zip > > > > SHA256: 7df2933b366aff8e1dc3abe9bafb3e8891186ca937d34d646952d43db624d4e2 > > SHA512: > > > > > 36c0f107b5a98388c2fb2c48d24f4df9980d9685a9b31d08c0a7a6a47b54de556ff368a8c622a5011dab4448274fc16f6e18c5d29368a81d003baa7c7382bd4d > > > > Release artifacts are signed with the following key: > > > > https://people.apache.org/keys/committer/pvillard.asc > > > > KEYS file is available on the Apache Distribution Repository: > > > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > Issues resolved for this version: 35 > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354832 > > > > Release note highlights can be found on the project wiki: > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.27.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. Then > > please vote: > > > > [] +1 Release this package as nifi-1.27.0 > > [] +0 no opinion > > [] -1 Do not release this package because... > > >
Re: [VOTE] Release Apache NiFi 1.27.0 (RC1)
I'm seeing SHA256 and SHA512 mismatches, also my automated RC script noticed your GPG key is expired. On Thu, Jun 27, 2024 at 5:11 PM Pierre Villard wrote: > Team, > > I am pleased to be calling this vote for the source release of Apache NiFi > 1.27.0. > > Please review the following guide for how to verify a release candidate > build: > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification > > The source being voted on the and the convenience binaries are available on > the Apache Distribution Repository: > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.27.0 > > The build artifacts are available on the Apache Nexus Repository: > > https://repository.apache.org/content/repositories/orgapachenifi-1272 > > Git Tag: nifi-1.27.0-RC1 > Git Commit ID: bd86d1f07fe8d0f45b72e91e925ee85ffa7ed143 > GitHub Commit Link: > > https://github.com/apache/nifi/commit/bd86d1f07fe8d0f45b72e91e925ee85ffa7ed143 > > Checksums of nifi-1.27.0-source-release.zip > > SHA256: 7df2933b366aff8e1dc3abe9bafb3e8891186ca937d34d646952d43db624d4e2 > SHA512: > > 36c0f107b5a98388c2fb2c48d24f4df9980d9685a9b31d08c0a7a6a47b54de556ff368a8c622a5011dab4448274fc16f6e18c5d29368a81d003baa7c7382bd4d > > Release artifacts are signed with the following key: > > https://people.apache.org/keys/committer/pvillard.asc > > KEYS file is available on the Apache Distribution Repository: > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > Issues resolved for this version: 35 > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354832 > > Release note highlights can be found on the project wiki: > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.27.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. Then > please vote: > > [] +1 Release this package as nifi-1.27.0 > [] +0 no opinion > [] -1 Do not release this package because... >
[VOTE] Release Apache NiFi 1.27.0 (RC1)
Team, I am pleased to be calling this vote for the source release of Apache NiFi 1.27.0. Please review the following guide for how to verify a release candidate build: https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification The source being voted on the and the convenience binaries are available on the Apache Distribution Repository: https://dist.apache.org/repos/dist/dev/nifi/nifi-1.27.0 The build artifacts are available on the Apache Nexus Repository: https://repository.apache.org/content/repositories/orgapachenifi-1272 Git Tag: nifi-1.27.0-RC1 Git Commit ID: bd86d1f07fe8d0f45b72e91e925ee85ffa7ed143 GitHub Commit Link: https://github.com/apache/nifi/commit/bd86d1f07fe8d0f45b72e91e925ee85ffa7ed143 Checksums of nifi-1.27.0-source-release.zip SHA256: 7df2933b366aff8e1dc3abe9bafb3e8891186ca937d34d646952d43db624d4e2 SHA512: 36c0f107b5a98388c2fb2c48d24f4df9980d9685a9b31d08c0a7a6a47b54de556ff368a8c622a5011dab4448274fc16f6e18c5d29368a81d003baa7c7382bd4d Release artifacts are signed with the following key: https://people.apache.org/keys/committer/pvillard.asc KEYS file is available on the Apache Distribution Repository: https://dist.apache.org/repos/dist/release/nifi/KEYS Issues resolved for this version: 35 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354832 Release note highlights can be found on the project wiki: https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.27.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. Then please vote: [] +1 Release this package as nifi-1.27.0 [] +0 no opinion [] -1 Do not release this package because...
Nifi Configuration Isue
Hello Team, We have issue without threenode nifi cluster with the following error . We are looking for the support to solve the issue. Could you please let us know how we can log an incident/request to get help from your team ? [image: image.png] Thanks, Ravali. -- Thanks & Regards Ravali Yalamanchali <http://www.verizon.com/> 700 hidden ridge Irving, TX, 75038
Re: [DISCUSS] Release Planning for NiFi 2.0.0-M4 and 1.26.1
Team, I'll get started with the release process. In light of the changes, I'll go with a 1.27 release as it's not only containing bug fixes. Thanks, Pierre Le mer. 26 juin 2024 à 00:01, David Handermann a écrit : > Team, > > Thanks for the replies thus far. In a conversation with Shane, and > reviewing the current status of the PR [1], it looks like there is a > bit more work to do, plus review, to get that completed. > > Other than that, I am planning to review the Python API PR for > NIFI-13427 [2] and then I think we are in a good position for an > initial release candidate build. > > Regards, > David Handermann > > [1] https://github.com/apache/nifi/pull/8974 > [2] https://github.com/apache/nifi/pull/9000 > > On Mon, Jun 17, 2024 at 11:12 AM Shane Ardell > wrote: > > > > Hi team, > > > > Pierre is correct that I'm aiming to have a PR open today to expose the > > flow analysis rules engine in the new UI. I'll be sure to address any > > feedback left on my PR asap. > > > > Best, > > Shane > > > > On Mon, Jun 17, 2024 at 12:03 PM Pierre Villard < > pierre.villard...@gmail.com> > > wrote: > > > > > Hi team, > > > > > > Happy to take care of the 1.26.1. > > > > > > I believe Shane will open a PR today to have the UI bits of the rules > > > engine available in the new UI. We may want to wait for this, assuming > this > > > would be merged quickly, to get as much feedback as possible on the > new UI. > > > > > > Very exciting to see all of this coming together! Thanks David for > starting > > > this discussion. > > > > > > Pierre > > > > > > Le lun. 17 juin 2024 à 17:39, David Handermann < > > > exceptionfact...@apache.org> > > > a écrit : > > > > > > > Team, > > > > > > > > With recent changes on the main branch to make the nifi-web-frontend > > > > module the default version of the user interface, we are in a good > > > > position for another milestone release of NiFi 2.0.0. > > > > > > > > As always, we also have a number of bug fixes and dependency upgrades > > > > that are ready for release. It seems helpful to have a Milestone 4 > > > > release version, with a focus on the new user interface, as it will > > > > provide an opportunity for additional feedback before a full general > > > > availability version of NiFi 2.0.0. Thanks again to Matt Gilman, Rob > > > > Fellows, and Scott Aslan for their incredible effort to rebuild the > > > > user interface on modern frameworks and libraries! > > > > > > > > Although NiFi 2.0.0 remains the primary focus, there have been > several > > > > important bug fixes applied to the support branch [1]. I renamed the > > > > 1.27.0 version to 1.26.1 since the number of changes and the types of > > > > changes are narrowly focused. Pierre Villard mentioned that he is > > > > ready to handle the Release Manager responsibilities for the 1.26.1 > > > > version, and I would be glad to handle the 2.0.0-M4 version. > > > > > > > > I am in the process of reviewing open pull requests, and I believe we > > > > are close to ready for release candidates this week. > > > > > > > > Regards, > > > > David Handermann > > > > > > > > [1] https://issues.apache.org/jira/projects/NIFI/versions/12354651 > > > > > > > >
Re: [DISCUSS] Release Planning for NiFi 2.0.0-M4 and 1.26.1
Team, Thanks for the replies thus far. In a conversation with Shane, and reviewing the current status of the PR [1], it looks like there is a bit more work to do, plus review, to get that completed. Other than that, I am planning to review the Python API PR for NIFI-13427 [2] and then I think we are in a good position for an initial release candidate build. Regards, David Handermann [1] https://github.com/apache/nifi/pull/8974 [2] https://github.com/apache/nifi/pull/9000 On Mon, Jun 17, 2024 at 11:12 AM Shane Ardell wrote: > > Hi team, > > Pierre is correct that I'm aiming to have a PR open today to expose the > flow analysis rules engine in the new UI. I'll be sure to address any > feedback left on my PR asap. > > Best, > Shane > > On Mon, Jun 17, 2024 at 12:03 PM Pierre Villard > wrote: > > > Hi team, > > > > Happy to take care of the 1.26.1. > > > > I believe Shane will open a PR today to have the UI bits of the rules > > engine available in the new UI. We may want to wait for this, assuming this > > would be merged quickly, to get as much feedback as possible on the new UI. > > > > Very exciting to see all of this coming together! Thanks David for starting > > this discussion. > > > > Pierre > > > > Le lun. 17 juin 2024 à 17:39, David Handermann < > > exceptionfact...@apache.org> > > a écrit : > > > > > Team, > > > > > > With recent changes on the main branch to make the nifi-web-frontend > > > module the default version of the user interface, we are in a good > > > position for another milestone release of NiFi 2.0.0. > > > > > > As always, we also have a number of bug fixes and dependency upgrades > > > that are ready for release. It seems helpful to have a Milestone 4 > > > release version, with a focus on the new user interface, as it will > > > provide an opportunity for additional feedback before a full general > > > availability version of NiFi 2.0.0. Thanks again to Matt Gilman, Rob > > > Fellows, and Scott Aslan for their incredible effort to rebuild the > > > user interface on modern frameworks and libraries! > > > > > > Although NiFi 2.0.0 remains the primary focus, there have been several > > > important bug fixes applied to the support branch [1]. I renamed the > > > 1.27.0 version to 1.26.1 since the number of changes and the types of > > > changes are narrowly focused. Pierre Villard mentioned that he is > > > ready to handle the Release Manager responsibilities for the 1.26.1 > > > version, and I would be glad to handle the 2.0.0-M4 version. > > > > > > I am in the process of reviewing open pull requests, and I believe we > > > are close to ready for release candidates this week. > > > > > > Regards, > > > David Handermann > > > > > > [1] https://issues.apache.org/jira/projects/NIFI/versions/12354651 > > > > >
Re: Nifi-2.0.M3 Install
Hi Venu, The image didn't go through but I suspect that you're running into the SNI issue. If that's the case, please share with us the steps you've taken to configure nifi.properties in your deployment. This blog post [1] may also be helpful. [1] https://medium.com/@chnzhoujun/how-to-resolve-sni-issue-when-upgrading-to-nifi-2-0-907e07d465c5 HTH, Pierre Le mar. 25 juin 2024 à 15:04, Gorantla, Venugopal EX1 a écrit : > Hi Team, > > I have installed NIfi-2.0.M3 in the ubuntu server. > Nifi service started successfully and Nifi url also generated. > > But when try accessing URL getting error as below : > URL : https://ec2-3-233-74-147.compute-1.amazonaws.com:9443/nifi > > > > Could you please help regarding this. > > Regards, > Venu G > > > > *IMPORTANT* - PLEASE READ: This electronic message, including its > attachments, is CONFIDENTIAL and may contain PROPRIETARY or LEGALLY > PRIVILEGED or PROTECTED information and is intended for the authorized > recipient of the sender. If you are not the intended recipient, you are > hereby notified that any use, disclosure, copying, or distribution of this > message or any of the information included in it is unauthorized and > strictly prohibited. If you have received this message in error, please > immediately notify the sender by reply e-mail and permanently delete this > message and its attachments, along with any copies thereof, from all > locations received (e.g., computer, mobile device, etc.). To the extent > permitted by law, we may monitor electronic communications for the purposes > of ensuring compliance with our legal and regulatory obligations and > internal policies. We may also collect email traffic headers for analyzing > patterns of network traffic and managing client relationships. For further > information see our privacy-policy > <https://www.iqvia.com/about-us/privacy/privacy-policy>. Thank you. > >
Re: Apache Nifi Compatibility with Oracle Linux 9
Hi, There should not be any particular issue running NiFi with Oracle Linux as NiFi is OS-agnostic and really just depends on the installed JDK. NiFi 1.9.2 is an extremely old version of NiFi and we would highly recommend upgrading to a more recent version of NiFi. HTH, Pierre Le mar. 25 juin 2024 à 15:03, a écrit : > Good Afternoon > > > > I am having trouble finding the information I am after online and was > hoping you could assist. > > > > Could you please let me know what version(s) of Oracle Linux Nifi 1.9.2 > supports and whether it can support a mixture of different versions of OL? > > > > Thanks in advance! > > > > > > *Fatima Jarjue* > SRE Associate > Secure Development, Networks > > > E: fatima.jar...@bt.com > > [image: BT Group] > > This email contains information from BT Group that might be privileged or > confidential. And it's only meant for the person above. If that's not you, > we're sorry - we must have sent it to you by mistake. Please email us to > let us know, and don't copy or forward it to anyone else. Thanks. > > We monitor our email systems and may record all our emails. > > British Telecommunications plc > R/O : 1 Braham Street, London, E1 8EE > Registered in England: No 180 > > British Telecommunications plc is authorised and regulated by Financial > Conduct Authority for the provision of consumer credit > > > > >
Nifi-2.0.M3 Install
Hi Team, I have installed NIfi-2.0.M3 in the ubuntu server. Nifi service started successfully and Nifi url also generated. But when try accessing URL getting error as below : URL : https://ec2-3-233-74-147.compute-1.amazonaws.com:9443/nifi [cid:image001.png@01DAC712.BCFC6FD0] Could you please help regarding this. Regards, Venu G IMPORTANT - PLEASE READ: This electronic message, including its attachments, is CONFIDENTIAL and may contain PROPRIETARY or LEGALLY PRIVILEGED or PROTECTED information and is intended for the authorized recipient of the sender. If you are not the intended recipient, you are hereby notified that any use, disclosure, copying, or distribution of this message or any of the information included in it is unauthorized and strictly prohibited. If you have received this message in error, please immediately notify the sender by reply e-mail and permanently delete this message and its attachments, along with any copies thereof, from all locations received (e.g., computer, mobile device, etc.). To the extent permitted by law, we may monitor electronic communications for the purposes of ensuring compliance with our legal and regulatory obligations and internal policies. We may also collect email traffic headers for analyzing patterns of network traffic and managing client relationships. For further information see our privacy-policy<https://www.iqvia.com/about-us/privacy/privacy-policy>. Thank you.
Apache Nifi Compatibility with Oracle Linux 9
Good Afternoon I am having trouble finding the information I am after online and was hoping you could assist. Could you please let me know what version(s) of Oracle Linux Nifi 1.9.2 supports and whether it can support a mixture of different versions of OL? Thanks in advance! Fatima Jarjue SRE Associate Secure Development, Networks E: fatima.jar...@bt.com<mailto:fatima.jar...@bt.com> [BT Group] This email contains information from BT Group that might be privileged or confidential. And it's only meant for the person above. If that's not you, we're sorry - we must have sent it to you by mistake. Please email us to let us know, and don't copy or forward it to anyone else. Thanks. We monitor our email systems and may record all our emails. British Telecommunications plc R/O : 1 Braham Street, London, E1 8EE Registered in England: No 180 British Telecommunications plc is authorised and regulated by Financial Conduct Authority for the provision of consumer credit
Re: [DISCUSS] Release Planning for NiFi 2.0.0-M4 and 1.26.1
Hi team, Pierre is correct that I'm aiming to have a PR open today to expose the flow analysis rules engine in the new UI. I'll be sure to address any feedback left on my PR asap. Best, Shane On Mon, Jun 17, 2024 at 12:03 PM Pierre Villard wrote: > Hi team, > > Happy to take care of the 1.26.1. > > I believe Shane will open a PR today to have the UI bits of the rules > engine available in the new UI. We may want to wait for this, assuming this > would be merged quickly, to get as much feedback as possible on the new UI. > > Very exciting to see all of this coming together! Thanks David for starting > this discussion. > > Pierre > > Le lun. 17 juin 2024 à 17:39, David Handermann < > exceptionfact...@apache.org> > a écrit : > > > Team, > > > > With recent changes on the main branch to make the nifi-web-frontend > > module the default version of the user interface, we are in a good > > position for another milestone release of NiFi 2.0.0. > > > > As always, we also have a number of bug fixes and dependency upgrades > > that are ready for release. It seems helpful to have a Milestone 4 > > release version, with a focus on the new user interface, as it will > > provide an opportunity for additional feedback before a full general > > availability version of NiFi 2.0.0. Thanks again to Matt Gilman, Rob > > Fellows, and Scott Aslan for their incredible effort to rebuild the > > user interface on modern frameworks and libraries! > > > > Although NiFi 2.0.0 remains the primary focus, there have been several > > important bug fixes applied to the support branch [1]. I renamed the > > 1.27.0 version to 1.26.1 since the number of changes and the types of > > changes are narrowly focused. Pierre Villard mentioned that he is > > ready to handle the Release Manager responsibilities for the 1.26.1 > > version, and I would be glad to handle the 2.0.0-M4 version. > > > > I am in the process of reviewing open pull requests, and I believe we > > are close to ready for release candidates this week. > > > > Regards, > > David Handermann > > > > [1] https://issues.apache.org/jira/projects/NIFI/versions/12354651 > > >
Re: [DISCUSS] Release Planning for NiFi 2.0.0-M4 and 1.26.1
Hi team, Happy to take care of the 1.26.1. I believe Shane will open a PR today to have the UI bits of the rules engine available in the new UI. We may want to wait for this, assuming this would be merged quickly, to get as much feedback as possible on the new UI. Very exciting to see all of this coming together! Thanks David for starting this discussion. Pierre Le lun. 17 juin 2024 à 17:39, David Handermann a écrit : > Team, > > With recent changes on the main branch to make the nifi-web-frontend > module the default version of the user interface, we are in a good > position for another milestone release of NiFi 2.0.0. > > As always, we also have a number of bug fixes and dependency upgrades > that are ready for release. It seems helpful to have a Milestone 4 > release version, with a focus on the new user interface, as it will > provide an opportunity for additional feedback before a full general > availability version of NiFi 2.0.0. Thanks again to Matt Gilman, Rob > Fellows, and Scott Aslan for their incredible effort to rebuild the > user interface on modern frameworks and libraries! > > Although NiFi 2.0.0 remains the primary focus, there have been several > important bug fixes applied to the support branch [1]. I renamed the > 1.27.0 version to 1.26.1 since the number of changes and the types of > changes are narrowly focused. Pierre Villard mentioned that he is > ready to handle the Release Manager responsibilities for the 1.26.1 > version, and I would be glad to handle the 2.0.0-M4 version. > > I am in the process of reviewing open pull requests, and I believe we > are close to ready for release candidates this week. > > Regards, > David Handermann > > [1] https://issues.apache.org/jira/projects/NIFI/versions/12354651 >
[DISCUSS] Release Planning for NiFi 2.0.0-M4 and 1.26.1
Team, With recent changes on the main branch to make the nifi-web-frontend module the default version of the user interface, we are in a good position for another milestone release of NiFi 2.0.0. As always, we also have a number of bug fixes and dependency upgrades that are ready for release. It seems helpful to have a Milestone 4 release version, with a focus on the new user interface, as it will provide an opportunity for additional feedback before a full general availability version of NiFi 2.0.0. Thanks again to Matt Gilman, Rob Fellows, and Scott Aslan for their incredible effort to rebuild the user interface on modern frameworks and libraries! Although NiFi 2.0.0 remains the primary focus, there have been several important bug fixes applied to the support branch [1]. I renamed the 1.27.0 version to 1.26.1 since the number of changes and the types of changes are narrowly focused. Pierre Villard mentioned that he is ready to handle the Release Manager responsibilities for the 1.26.1 version, and I would be glad to handle the 2.0.0-M4 version. I am in the process of reviewing open pull requests, and I believe we are close to ready for release candidates this week. Regards, David Handermann [1] https://issues.apache.org/jira/projects/NIFI/versions/12354651
Re: Thoughts on various ways to help drive NiFi and the community forward
Mathew, certainly! I've been meaning to update the blog too. Email me at mattyb...@apache.org and we'll get 'em up there :) Thanks, Matt On Sat, Jun 15, 2024 at 2:46 PM Mathew Kiprop wrote: > +1 to all subjects addressed Joe. > > I have been planning to improve developer advocacy around scripting > components. The groovy scripts have been one of my best tools to build > flows in NiFi (Rest API development , complex data structures > transformation, controlled flows scheduling…..). I’ll take this opportunity > to ask Mat Burges whether I can contribute some of my work to > http://funnifi.blogspot.com/?m=1. > > Mathew > > On Sat, 15 Jun 2024 at 21:03, Joe Witt wrote: > > > Team, > > > > We are seeing an increase in the unique contributors on a monthly basis > to > > NiFi and a clear and steady increase in the overall contribution rate > over > > the past 1-2 years in particular. This is awesome but we do have > important > > problems to cover and we need to make it easier to help newer > contributors > > know where to jump in and add the most value. > > > > For sure people will contribute various things just because they have a > > particular interest such as some new extension, etc.. But from a > community > > direction perspective there are things we need to continue to improve > upon > > and we want to help make the path to committership and PMC membership > more > > clear as a function of adding value to the community. > > > > So not necessarily ordered, here are some key things I've observed that > > need more attention and are among the most valuable things for the health > > of the nifi system and community. > > > > Dependency Management > > > > This is a hugely important area as we have a massive amount of > dependencies > > and this work is just plain not that fun. But if we want to present a > > beautiful landscape we need to pull weeds. We need to reduce > dependencies > > and keep things recent. This is largely accomplished today by a very > small > > group of people. We have to increase the contribution level here or > > perhaps the automation level. We have tooling that is helping now but > > still needs more attention. > > > > Vulnerability Management particular as it relates to dependencies > > > > Related to dependency management but broader. This one at times requires > > us to do more than simply maintain dependencies. It sometimes forces us > to > > change libraries and sometimes even makes maintaining > > compatibility/configuration complicated. These are among the most > critical > > and most difficult tasks to take on. This is largely done today by an > > extremely small group of people. > > > > Maintenance of extensions > > > > We have a ton of components in NiFi. Obviously not all of them really do > > require active maintenance but there is often a contribute and forget > model > > involved. For us to keep these broad range of components under community > > care they need active maintenance. I already mentioned the dependency > > factor above but the broader point here is that APIs/versions of systems > > evolve. We need to be staying up to date. There are systems like Kafka, > > Elastic, Mongo, Relational Databases, etc.. that we should always be > > supporting the latest on. These are among the most wildly popular > sources > > and destinations. We do tend to fall behind here and this is powerfully > > useful for people to contribute to. These are the things our users > > actually use NiFi for! > > > > Maintenance of things other than core nifi > > > > If you look at components ancillary to NiFi they receive far less > attention > > and effort trending toward them going away. The NiFi registry is a great > > example of this as NiFi MiNiFi Java for instance. These are things which > > are useful and indeed there is a decent user base in both cases. But > they > > require more active maintenance than they get. We need to evolve when it > > comes to security methods offered for authn/authz and that takes focus. > > > > Performance analysis and improvements targeted as a result > > > > This is done very rarely as far as I can tell outside a couple of people > > who I'm sure we could all name in a few seconds. The codebase is large > and > > Java and other parts evolve. Continually emphasizing faster and more > > efficient operations is vital to NiFi's continued growth in the > > community at large. People who spend time running NiFi in a measured > > man
Re: Thoughts on various ways to help drive NiFi and the community forward
+1 to all subjects addressed Joe. I have been planning to improve developer advocacy around scripting components. The groovy scripts have been one of my best tools to build flows in NiFi (Rest API development , complex data structures transformation, controlled flows scheduling…..). I’ll take this opportunity to ask Mat Burges whether I can contribute some of my work to http://funnifi.blogspot.com/?m=1. Mathew On Sat, 15 Jun 2024 at 21:03, Joe Witt wrote: > Team, > > We are seeing an increase in the unique contributors on a monthly basis to > NiFi and a clear and steady increase in the overall contribution rate over > the past 1-2 years in particular. This is awesome but we do have important > problems to cover and we need to make it easier to help newer contributors > know where to jump in and add the most value. > > For sure people will contribute various things just because they have a > particular interest such as some new extension, etc.. But from a community > direction perspective there are things we need to continue to improve upon > and we want to help make the path to committership and PMC membership more > clear as a function of adding value to the community. > > So not necessarily ordered, here are some key things I've observed that > need more attention and are among the most valuable things for the health > of the nifi system and community. > > Dependency Management > > This is a hugely important area as we have a massive amount of dependencies > and this work is just plain not that fun. But if we want to present a > beautiful landscape we need to pull weeds. We need to reduce dependencies > and keep things recent. This is largely accomplished today by a very small > group of people. We have to increase the contribution level here or > perhaps the automation level. We have tooling that is helping now but > still needs more attention. > > Vulnerability Management particular as it relates to dependencies > > Related to dependency management but broader. This one at times requires > us to do more than simply maintain dependencies. It sometimes forces us to > change libraries and sometimes even makes maintaining > compatibility/configuration complicated. These are among the most critical > and most difficult tasks to take on. This is largely done today by an > extremely small group of people. > > Maintenance of extensions > > We have a ton of components in NiFi. Obviously not all of them really do > require active maintenance but there is often a contribute and forget model > involved. For us to keep these broad range of components under community > care they need active maintenance. I already mentioned the dependency > factor above but the broader point here is that APIs/versions of systems > evolve. We need to be staying up to date. There are systems like Kafka, > Elastic, Mongo, Relational Databases, etc.. that we should always be > supporting the latest on. These are among the most wildly popular sources > and destinations. We do tend to fall behind here and this is powerfully > useful for people to contribute to. These are the things our users > actually use NiFi for! > > Maintenance of things other than core nifi > > If you look at components ancillary to NiFi they receive far less attention > and effort trending toward them going away. The NiFi registry is a great > example of this as NiFi MiNiFi Java for instance. These are things which > are useful and indeed there is a decent user base in both cases. But they > require more active maintenance than they get. We need to evolve when it > comes to security methods offered for authn/authz and that takes focus. > > Performance analysis and improvements targeted as a result > > This is done very rarely as far as I can tell outside a couple of people > who I'm sure we could all name in a few seconds. The codebase is large and > Java and other parts evolve. Continually emphasizing faster and more > efficient operations is vital to NiFi's continued growth in the > community at large. People who spend time running NiFi in a measured > manner with realistic flows and doing things like profiling for CPU, > memory, etc.. and finding bottlenecks and offering solutions - absolutely > can be high impact and valuable. Even if not at a point where a confident > contribution can be made, the very act of doing this level of evaluation > and flagging concerns is valuable. > > Improvements related to tests both unit and integration - but also for > users of NiFi > > As part of our push to NiFi 2.0 we have been running these tests far more > often and more complete than ever before. Github Actions now pretty much > does run all the things. We've deleted a wild amount of junk tests that >
Thoughts on various ways to help drive NiFi and the community forward
Team, We are seeing an increase in the unique contributors on a monthly basis to NiFi and a clear and steady increase in the overall contribution rate over the past 1-2 years in particular. This is awesome but we do have important problems to cover and we need to make it easier to help newer contributors know where to jump in and add the most value. For sure people will contribute various things just because they have a particular interest such as some new extension, etc.. But from a community direction perspective there are things we need to continue to improve upon and we want to help make the path to committership and PMC membership more clear as a function of adding value to the community. So not necessarily ordered, here are some key things I've observed that need more attention and are among the most valuable things for the health of the nifi system and community. Dependency Management This is a hugely important area as we have a massive amount of dependencies and this work is just plain not that fun. But if we want to present a beautiful landscape we need to pull weeds. We need to reduce dependencies and keep things recent. This is largely accomplished today by a very small group of people. We have to increase the contribution level here or perhaps the automation level. We have tooling that is helping now but still needs more attention. Vulnerability Management particular as it relates to dependencies Related to dependency management but broader. This one at times requires us to do more than simply maintain dependencies. It sometimes forces us to change libraries and sometimes even makes maintaining compatibility/configuration complicated. These are among the most critical and most difficult tasks to take on. This is largely done today by an extremely small group of people. Maintenance of extensions We have a ton of components in NiFi. Obviously not all of them really do require active maintenance but there is often a contribute and forget model involved. For us to keep these broad range of components under community care they need active maintenance. I already mentioned the dependency factor above but the broader point here is that APIs/versions of systems evolve. We need to be staying up to date. There are systems like Kafka, Elastic, Mongo, Relational Databases, etc.. that we should always be supporting the latest on. These are among the most wildly popular sources and destinations. We do tend to fall behind here and this is powerfully useful for people to contribute to. These are the things our users actually use NiFi for! Maintenance of things other than core nifi If you look at components ancillary to NiFi they receive far less attention and effort trending toward them going away. The NiFi registry is a great example of this as NiFi MiNiFi Java for instance. These are things which are useful and indeed there is a decent user base in both cases. But they require more active maintenance than they get. We need to evolve when it comes to security methods offered for authn/authz and that takes focus. Performance analysis and improvements targeted as a result This is done very rarely as far as I can tell outside a couple of people who I'm sure we could all name in a few seconds. The codebase is large and Java and other parts evolve. Continually emphasizing faster and more efficient operations is vital to NiFi's continued growth in the community at large. People who spend time running NiFi in a measured manner with realistic flows and doing things like profiling for CPU, memory, etc.. and finding bottlenecks and offering solutions - absolutely can be high impact and valuable. Even if not at a point where a confident contribution can be made, the very act of doing this level of evaluation and flagging concerns is valuable. Improvements related to tests both unit and integration - but also for users of NiFi As part of our push to NiFi 2.0 we have been running these tests far more often and more complete than ever before. Github Actions now pretty much does run all the things. We've deleted a wild amount of junk tests that would always fail or were spurious or required some complex local access/setup and therefore nobody ever ran them. We need to always improve coverage but we want to make tests faster/more efficient and more leveraging of things like test containers would be highly valuable. Importantly though here I also mean to highlight we need to do a lot more for users of NiFi that want to create automated tests for their flows. We should make it easy for them to provide a flow definition or perhaps a DSL for their flow and write tests which would leverage actual nifi to validate a given input results in an expected output. This is something that would add a ton of value for our user base but also lead into some really powerful testing we can do against our own framework. Development of blogs/videos/conference presentations/social media posts
RE: RE: Adding non-standard processors to Nifi 2.0
I think I figured it out… NullPointerException at FlowController.java:873 was the clue. https://github.com/apache/nifi/blob/b1500ad0317578f903a441d327f44af255015af7/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/FlowController.java#L873 Even though documentations mention “default” values, I needed to actually *add* all the keys to the nifi.properties. [ec2-user@--- nifi]$ cat ./conf/nifi.properties | grep -i --color=auto python # for python extensions nifi.python.command=/usr/bin/python3 nifi.python.extensions.source.directory.default=/opt/nifi/nifi-current/python_extensions nifi.python.working.directory=./work/python nifi.python.framework.source.directory=./python/framework nifi.python.max.processes.per.extension.type=10 nifi.python.max.processes=100 On 2024/06/12 17:51:19 "Nguyen, Kyle" wrote: > After a bit of digging, it looks like I didn’t have `nifi.python.command` > defined in my `nifi.properties`. But once I enable it, I get a > `NullPointerException`, all other things equal. Any help? > nifi_container_persistent | Caused by: java.lang.NullPointerException: > null > nifi_container_persistent | at > java.base/java.io.File.(File.java:278) > nifi_container_persistent | at > org.apache.nifi.controller.FlowController.createPythonBridge(FlowController.java:873) > nifi_container_persistent | at > org.apache.nifi.controller.FlowController.(FlowController.java:573) > nifi_container_persistent | at > org.apache.nifi.controller.FlowController.createStandaloneInstance(FlowController.java:411) > nifi_container_persistent | at > org.apache.nifi.spring.FlowControllerFactoryBean.getObject(FlowControllerFactoryBean.java:83) > nifi_container_persistent | at > org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySupport.java:182) > nifi_container_persistent | ... 120 common frames omitted > > > > [ec2-user@ip-- nifi]$ cat ./conf/nifi.properties | grep -i --color=auto > python > > # for python extensions > > nifi.python.command=python3 > > nifi.python.extensions.source.directory.default=/opt/nifi/nifi-current/python_extensions > > > > On 2024/06/12 16:16:52 "Nguyen, Kyle" wrote: > > Hi guys, > > > > I’m aware how to add custom processors (via nar’s -> extensions folder). > > But how do you add processors that area already on the git? E.g. > > > > > > > * > > https://github.com/apache/nifi/blob/main/nifi-python-extensions/nifi-openai-module/src/main/python/PromptChatGPT.py > > > > > Bonus question: How does it work? How are some processors defined but > > don’t make it into the standard install (our install is via the docker > > image `apache/nifi:2.0.0-M3`)? Thanks! > > > > > > > [cid:image001.png@01DABCC1.BE66A940] > > Kyle Nguyen > > Corporate Technology, Software Engineer > > > > Millennium Management LLC > > 399 Park Avenue | New York, NY 10022 > > +1.212.708.1366 | +1.929.837.1788 > > mlp.com<https://www.mlp.com/home/> > > > > > > > > > > ## > > > > The information contained in this communication is confidential and > > > > may contain information that is privileged or exempt from disclosure > > > > under applicable law. If you are not a named addressee, please notify > > > > the sender immediately and delete this email from your system. > > > > If you have received this communication, and are not a named > > > > recipient, you are hereby notified that any dissemination, > > > > distribution or copying of this communication is strictly prohibited. > > > > ## > > > > > ## > > The information contained in this communication is confidential and > > may contain information that is privileged or exempt from disclosure > > under applicable law. If you are not a named addressee, please notify > > the sender immediately and delete this email from your system. > > If you have received this communication, and are not a named > > recipient, you are hereby notified that any dissemination, > > distribution or copying of this communication is strictly prohibited. > > ## > ## The information contained in this communication is confidential and may contain information that is privileged or exempt from disclosure under applicable law. If you are not a named addressee, please notify the sender immediately and delete this email from your system. If you have received this communication, and are not a named recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. ##
Re: Adding non-standard processors to Nifi 2.0
Hello, The provided nifi.properties should have three properties related to python directories, the defaults are: nifi.python.framework.source.directory=./python/framework nifi.python.extensions.source.directory.default=./python/extensions nifi.python.working.directory=./work/python One of those is missing and causing the NullPointerException. Thanks, Bryan On Wed, Jun 12, 2024 at 1:55 PM Nguyen, Kyle wrote: > > After a bit of digging, it looks like I didn’t have `nifi.python.command` > defined in my `nifi.properties`. But once I enable it, I get a > `NullPointerException`, all other things equal. Any help? > nifi_container_persistent | Caused by: java.lang.NullPointerException: > null > nifi_container_persistent | at > java.base/java.io.File.(File.java:278) > nifi_container_persistent | at > org.apache.nifi.controller.FlowController.createPythonBridge(FlowController.java:873) > nifi_container_persistent | at > org.apache.nifi.controller.FlowController.(FlowController.java:573) > nifi_container_persistent | at > org.apache.nifi.controller.FlowController.createStandaloneInstance(FlowController.java:411) > nifi_container_persistent | at > org.apache.nifi.spring.FlowControllerFactoryBean.getObject(FlowControllerFactoryBean.java:83) > nifi_container_persistent | at > org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySupport.java:182) > nifi_container_persistent | ... 120 common frames omitted > > > > [ec2-user@ip-- nifi]$ cat ./conf/nifi.properties | grep -i --color=auto > python > > # for python extensions > > nifi.python.command=python3 > > nifi.python.extensions.source.directory.default=/opt/nifi/nifi-current/python_extensions > > > > On 2024/06/12 16:16:52 "Nguyen, Kyle" wrote: > > Hi guys, > > > > I’m aware how to add custom processors (via nar’s -> extensions folder). > > But how do you add processors that area already on the git? E.g. > > > > > > > * > > https://github.com/apache/nifi/blob/main/nifi-python-extensions/nifi-openai-module/src/main/python/PromptChatGPT.py > > > > > Bonus question: How does it work? How are some processors defined but > > don’t make it into the standard install (our install is via the docker > > image `apache/nifi:2.0.0-M3`)? Thanks! > > > > > > > [cid:image001.png@01DABCC1.BE66A940] > > Kyle Nguyen > > Corporate Technology, Software Engineer > > > > Millennium Management LLC > > 399 Park Avenue | New York, NY 10022 > > +1.212.708.1366 | +1.929.837.1788 > > mlp.com<https://www.mlp.com/home/> > > > > > > > > > > ## > > > > The information contained in this communication is confidential and > > > > may contain information that is privileged or exempt from disclosure > > > > under applicable law. If you are not a named addressee, please notify > > > > the sender immediately and delete this email from your system. > > > > If you have received this communication, and are not a named > > > > recipient, you are hereby notified that any dissemination, > > > > distribution or copying of this communication is strictly prohibited. > > > > ## > > > > > ## > > The information contained in this communication is confidential and > > may contain information that is privileged or exempt from disclosure > > under applicable law. If you are not a named addressee, please notify > > the sender immediately and delete this email from your system. > > If you have received this communication, and are not a named > > recipient, you are hereby notified that any dissemination, > > distribution or copying of this communication is strictly prohibited. > > ##
RE: Adding non-standard processors to Nifi 2.0
After a bit of digging, it looks like I didn’t have `nifi.python.command` defined in my `nifi.properties`. But once I enable it, I get a `NullPointerException`, all other things equal. Any help? nifi_container_persistent | Caused by: java.lang.NullPointerException: null nifi_container_persistent | at java.base/java.io.File.(File.java:278) nifi_container_persistent | at org.apache.nifi.controller.FlowController.createPythonBridge(FlowController.java:873) nifi_container_persistent | at org.apache.nifi.controller.FlowController.(FlowController.java:573) nifi_container_persistent | at org.apache.nifi.controller.FlowController.createStandaloneInstance(FlowController.java:411) nifi_container_persistent | at org.apache.nifi.spring.FlowControllerFactoryBean.getObject(FlowControllerFactoryBean.java:83) nifi_container_persistent | at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySupport.java:182) nifi_container_persistent | ... 120 common frames omitted [ec2-user@ip-- nifi]$ cat ./conf/nifi.properties | grep -i --color=auto python # for python extensions nifi.python.command=python3 nifi.python.extensions.source.directory.default=/opt/nifi/nifi-current/python_extensions On 2024/06/12 16:16:52 "Nguyen, Kyle" wrote: > Hi guys, > > I’m aware how to add custom processors (via nar’s -> extensions folder). But > how do you add processors that area already on the git? E.g. > > > * > https://github.com/apache/nifi/blob/main/nifi-python-extensions/nifi-openai-module/src/main/python/PromptChatGPT.py > > Bonus question: How does it work? How are some processors defined but don’t > make it into the standard install (our install is via the docker image > `apache/nifi:2.0.0-M3`)? Thanks! > > > [cid:image001.png@01DABCC1.BE66A940] > Kyle Nguyen > Corporate Technology, Software Engineer > > Millennium Management LLC > 399 Park Avenue | New York, NY 10022 > +1.212.708.1366 | +1.929.837.1788 > mlp.com<https://www.mlp.com/home/> > > > > > ## > > The information contained in this communication is confidential and > > may contain information that is privileged or exempt from disclosure > > under applicable law. If you are not a named addressee, please notify > > the sender immediately and delete this email from your system. > > If you have received this communication, and are not a named > > recipient, you are hereby notified that any dissemination, > > distribution or copying of this communication is strictly prohibited. > > ## > ## The information contained in this communication is confidential and may contain information that is privileged or exempt from disclosure under applicable law. If you are not a named addressee, please notify the sender immediately and delete this email from your system. If you have received this communication, and are not a named recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. ##
Adding non-standard processors to Nifi 2.0
Hi guys, I’m aware how to add custom processors (via nar’s -> extensions folder). But how do you add processors that area already on the git? E.g. * https://github.com/apache/nifi/blob/main/nifi-python-extensions/nifi-openai-module/src/main/python/PromptChatGPT.py Bonus question: How does it work? How are some processors defined but don’t make it into the standard install (our install is via the docker image `apache/nifi:2.0.0-M3`)? Thanks! [cid:image001.png@01DABCC1.BE66A940] Kyle Nguyen Corporate Technology, Software Engineer Millennium Management LLC 399 Park Avenue | New York, NY 10022 +1.212.708.1366 | +1.929.837.1788 mlp.com<https://www.mlp.com/home/> ## The information contained in this communication is confidential and may contain information that is privileged or exempt from disclosure under applicable law. If you are not a named addressee, please notify the sender immediately and delete this email from your system. If you have received this communication, and are not a named recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. ##
NiFi 2.0-M3 cluster
Hello.
I am trying to set up a cluster of 3 nodes in Docker containers. I am using
configuration below. But I am getting an error:
INFO [main] o.a.n.c.c.n.LeaderElectionNodeProtocolSender Determined that
Cluster Coordinator is located at 7f0306ee9e56:8082; will use this address for
sending heartbeat messages 2024-06-01 17:31:03,529 INFO [main]
o.a.n.c.p.AbstractNodeProtocolSender Cluster Coordinator is located at
7f0306ee9e56/:8082. Will send Cluster Connection Request to this
address 2024-06-01 17:31:03,572 WARN [main]
o.a.nifi.controller.StandardFlowService Failed to connect to cluster due to:
org.apache.nifi.cluster.protocol.ProtocolException: Failed marshalling
'CONNECTION_REQUEST' protocol message due to:
javax.net.ssl.SSLHandshakeException: PKIX path validation failed:
java.security.cert.CertPathValidatorException: Path does not chain with any of
the trust anchors
I was using the same config for NiFi 1.x version and it was working fine, but
with NiFi 2.0 - isn't. Can you please help me with cluster set up? Do I need
to set up a truststore and keystore? Can nodes communicate in non-secure mode?
Maybe you have some example docker-compose configs or you can forward me to
right direction?
Also, is it possible to use Nginx as reverse proxy behind the cluster? LIke
this:
location / {
proxy_set_header Host $http_host;
proxy_set_header X-ProxyScheme https;
proxy_set_header X-ProxyPort 8443;
proxy_pass https://nifi01:8443/;
}
Thank you.
My docker-compose.yml:
services:
zookeeper:
hostname: zookeeper
container_name: zookeeper
image: "bitnami/zookeeper:latest"
environment:
- ALLOW_ANONYMOUS_LOGIN=yes
networks:
- nifinet
nifi01:
image: apache/nifi:2.0.0-M3
container_name: nifi01
ports:
- "8443:8443"
- "7443:7443"
- "8080:8080"
networks:
- nifinet
environment:
- NIFI_SENSITIVE_PROPS_KEY=ctsBtRBKHRAx69EqUghvvgEvjnaLjFEB
- NIFI_WEB_HTTPS_PORT=8443
- NIFI_CLUSTER_NODE_ADDRESS=nifi01
- SINGLE_USER_CREDENTIALS_USERNAME=admin
- SINGLE_USER_CREDENTIALS_PASSWORD=ctsBtRBKHRAx69EqUghvvgEvjnaLjFEB
- NIFI_WEB_HTTP_PORT=8080
- NIFI_CLUSTER_IS_NODE=true
- NIFI_CLUSTER_NODE_PROTOCOL_PORT=8082
- NIFI_ZK_CONNECT_STRING=zookeeper:2181
- NIFI_ELECTION_MAX_WAIT=1 min
nifi02:
image: apache/nifi:2.0.0-M3
container_name: nifi02
ports:
- "18443:8443"
- "17443:7443"
- "18080:8080"
networks:
- nifinet
environment:
- NIFI_SENSITIVE_PROPS_KEY=ctsBtRBKHRAx69EqUghvvgEvjnaLjFEB
- NIFI_WEB_HTTPS_PORT=8443
- NIFI_CLUSTER_NODE_ADDRESS=nifi02
- SINGLE_USER_CREDENTIALS_USERNAME=admin
- SINGLE_USER_CREDENTIALS_PASSWORD=ctsBtRBKHRAx69EqUghvvgEvjnaLjFEB
- NIFI_WEB_HTTP_PORT=8080
- NIFI_CLUSTER_IS_NODE=true
- NIFI_CLUSTER_NODE_PROTOCOL_PORT=8082
- NIFI_ZK_CONNECT_STRING=zookeeper:2181
- NIFI_ELECTION_MAX_WAIT=1 min
nifi03:
image: apache/nifi:2.0.0-M3
container_name: nifi03
ports:
- "28443:8443"
- "27443:7443"
- "28080:8080"
networks:
- nifinet
environment:
- NIFI_SENSITIVE_PROPS_KEY=ctsBtRBKHRAx69EqUghvvgEvjnaLjFEB
- NIFI_WEB_HTTPS_PORT=8443
- NIFI_CLUSTER_NODE_ADDRESS=nifi03
- SINGLE_USER_CREDENTIALS_USERNAME=admin
- SINGLE_USER_CREDENTIALS_PASSWORD=ctsBtRBKHRAx69EqUghvvgEvjnaLjFEB
- NIFI_WEB_HTTP_PORT=8080
- NIFI_CLUSTER_IS_NODE=true
- NIFI_CLUSTER_NODE_PROTOCOL_PORT=8082
- NIFI_ZK_CONNECT_STRING=zookeeper:2181
- NIFI_ELECTION_MAX_WAIT=1
networks:
nifinet:
driver: bridge
[RESULT][VOTE] Release Apache NiFi NAR Maven Plugin 2.0.0
Apache NiFi Community, I am pleased to announce that the 2.0.0 release of Apache NiFi NAR Maven Plugin passes: 4 +1 (binding) votes 1 +1 (non-binding) votes 0 0 votes 0 -1 votes Thanks to all who helped make this release possible! The release artifacts will be published in the next 24 hours. Here is the vote thread: https://lists.apache.org/thread/kbrhjf72p3brbc17z3h16kh06zhnzx5r Thanks, Pierre
Re: [VOTE] Release Apache NiFi NAR Maven Plugin 2.0.0
+1 binding Le jeu. 23 mai 2024 à 19:40, Joe Witt a écrit : > +1 binding > > On Thu, May 23, 2024 at 10:33 AM Matt Burgess wrote: > > > +1 binding, verified the commit hash, applied the patch to NiFi main and > > verified the NAR Maven plugin works as expected. > > > > Thanks for RM'ing Pierre! > > > > On Wed, May 22, 2024 at 7:31 AM Pierre Villard < > > pierre.villard...@gmail.com> > > wrote: > > > > > Hello Apache NiFi Community, > > > > > > I am pleased to be calling this vote for the source release of Apache > > NiFi > > > NAR Maven Plugin 2.0.0. This new release is intended to be used with > NiFi > > > 2+. > > > > > > The source being voted upon, including signatures, digests, etc. can be > > > found at: > > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-nar-maven-plugin-2.0.0/ > > > > > > A helpful reminder on how the release candidate verification process > > works: > > > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+NAR+Maven+Plugin+release+candidate > > > > > > Please note that when trying this release, some changes are expected on > > the > > > NiFi side as proposed in the PR: > > https://github.com/apache/nifi/pull/8860 > > > > > > The Git tag is nifi-maven-2.0.0-RC1 > > > The Git commit ID is d0de49a34a1197988eaa007d28e6eb20ab6d701f > > > > > > > > > https://gitbox.apache.org/repos/asf?p=nifi-maven.git;a=commit;h=d0de49a34a1197988eaa007d28e6eb20ab6d701f > > > > > > Checksums of nifi-nar-maven-plugin-2.0.0-source-release.zip: > > > SHA256: > ae889c843a82c4823fca0bf5fedf275dbb812c2b11e25ae26b0bd4ad7d26ccae > > > SHA512: > > > > > > > > > c9afefb093d8b9568012d6697f302eb4a138f0a65a7045eaeb1bff551fb4bff23c805294700ca20984a3493eb61fe80a39d8b5b393afc85cf3f6ab1a28df831c > > > > > > Release artifacts are signed with the following key: > > > https://people.apache.org/keys/committer/pvillard.asc > > > > > > KEYS file available here: > > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > > > 5 issues were closed/resolved for this release: > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354745 > > > > > > Release note highlights can be found here: > > > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiNARMavenPluginVersion2.0.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. Then please vote: > > > > > > [ ] +1 Release this package as nifi-nar-maven-plugin-2.0.0 > > > [ ] +0 no opinion > > > [ ] -1 Do not release this package because … > > > > > >
Re: [VOTE] Release Apache NiFi NAR Maven Plugin 2.0.0
+1 binding On Thu, May 23, 2024 at 10:33 AM Matt Burgess wrote: > +1 binding, verified the commit hash, applied the patch to NiFi main and > verified the NAR Maven plugin works as expected. > > Thanks for RM'ing Pierre! > > On Wed, May 22, 2024 at 7:31 AM Pierre Villard < > pierre.villard...@gmail.com> > wrote: > > > Hello Apache NiFi Community, > > > > I am pleased to be calling this vote for the source release of Apache > NiFi > > NAR Maven Plugin 2.0.0. This new release is intended to be used with NiFi > > 2+. > > > > The source being voted upon, including signatures, digests, etc. can be > > found at: > > https://dist.apache.org/repos/dist/dev/nifi/nifi-nar-maven-plugin-2.0.0/ > > > > A helpful reminder on how the release candidate verification process > works: > > > > > https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+NAR+Maven+Plugin+release+candidate > > > > Please note that when trying this release, some changes are expected on > the > > NiFi side as proposed in the PR: > https://github.com/apache/nifi/pull/8860 > > > > The Git tag is nifi-maven-2.0.0-RC1 > > The Git commit ID is d0de49a34a1197988eaa007d28e6eb20ab6d701f > > > > > https://gitbox.apache.org/repos/asf?p=nifi-maven.git;a=commit;h=d0de49a34a1197988eaa007d28e6eb20ab6d701f > > > > Checksums of nifi-nar-maven-plugin-2.0.0-source-release.zip: > > SHA256: ae889c843a82c4823fca0bf5fedf275dbb812c2b11e25ae26b0bd4ad7d26ccae > > SHA512: > > > > > c9afefb093d8b9568012d6697f302eb4a138f0a65a7045eaeb1bff551fb4bff23c805294700ca20984a3493eb61fe80a39d8b5b393afc85cf3f6ab1a28df831c > > > > Release artifacts are signed with the following key: > > https://people.apache.org/keys/committer/pvillard.asc > > > > KEYS file available here: > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > 5 issues were closed/resolved for this release: > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354745 > > > > Release note highlights can be found here: > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiNARMavenPluginVersion2.0.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. Then please vote: > > > > [ ] +1 Release this package as nifi-nar-maven-plugin-2.0.0 > > [ ] +0 no opinion > > [ ] -1 Do not release this package because … > > >
Re: [VOTE] Release Apache NiFi NAR Maven Plugin 2.0.0
+1 binding, verified the commit hash, applied the patch to NiFi main and verified the NAR Maven plugin works as expected. Thanks for RM'ing Pierre! On Wed, May 22, 2024 at 7:31 AM Pierre Villard wrote: > Hello Apache NiFi Community, > > I am pleased to be calling this vote for the source release of Apache NiFi > NAR Maven Plugin 2.0.0. This new release is intended to be used with NiFi > 2+. > > The source being voted upon, including signatures, digests, etc. can be > found at: > https://dist.apache.org/repos/dist/dev/nifi/nifi-nar-maven-plugin-2.0.0/ > > A helpful reminder on how the release candidate verification process works: > > https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+NAR+Maven+Plugin+release+candidate > > Please note that when trying this release, some changes are expected on the > NiFi side as proposed in the PR: https://github.com/apache/nifi/pull/8860 > > The Git tag is nifi-maven-2.0.0-RC1 > The Git commit ID is d0de49a34a1197988eaa007d28e6eb20ab6d701f > > https://gitbox.apache.org/repos/asf?p=nifi-maven.git;a=commit;h=d0de49a34a1197988eaa007d28e6eb20ab6d701f > > Checksums of nifi-nar-maven-plugin-2.0.0-source-release.zip: > SHA256: ae889c843a82c4823fca0bf5fedf275dbb812c2b11e25ae26b0bd4ad7d26ccae > SHA512: > > c9afefb093d8b9568012d6697f302eb4a138f0a65a7045eaeb1bff551fb4bff23c805294700ca20984a3493eb61fe80a39d8b5b393afc85cf3f6ab1a28df831c > > Release artifacts are signed with the following key: > https://people.apache.org/keys/committer/pvillard.asc > > KEYS file available here: > https://dist.apache.org/repos/dist/release/nifi/KEYS > > 5 issues were closed/resolved for this release: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354745 > > Release note highlights can be found here: > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiNARMavenPluginVersion2.0.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. Then please vote: > > [ ] +1 Release this package as nifi-nar-maven-plugin-2.0.0 > [ ] +0 no opinion > [ ] -1 Do not release this package because … >
Re: [VOTE] Release Apache NiFi NAR Maven Plugin 2.0.0
+1 (non-binding) - Verified signatures and hashes - Applied NIFI-13267 and built NiFi with NAR Maven plugin 2.0.0 using Maven 3.9.6 on macOS 13.5 with Zulu21.28+85-CA7 Verified [NIFI-12226] - Maven plugin: Add flag to skip doc generation. Thanks for RM'ing, Pierre! On Thu, May 23, 2024 at 1:40 PM Bryan Bende wrote: > +1 binding > > - Verified everything in release helper > - Built the referenced NiFi PR with the 2.0.0 plugin > - Verified one of the changes for attaching the manifest xml as a build > artifact > > Thanks Pierre! > > On Wed, May 22, 2024 at 7:31 AM Pierre Villard > wrote: > > > > Hello Apache NiFi Community, > > > > I am pleased to be calling this vote for the source release of Apache > NiFi > > NAR Maven Plugin 2.0.0. This new release is intended to be used with NiFi > > 2+. > > > > The source being voted upon, including signatures, digests, etc. can be > > found at: > > https://dist.apache.org/repos/dist/dev/nifi/nifi-nar-maven-plugin-2.0.0/ > > > > A helpful reminder on how the release candidate verification process > works: > > > https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+NAR+Maven+Plugin+release+candidate > > > > Please note that when trying this release, some changes are expected on > the > > NiFi side as proposed in the PR: > https://github.com/apache/nifi/pull/8860 > > > > The Git tag is nifi-maven-2.0.0-RC1 > > The Git commit ID is d0de49a34a1197988eaa007d28e6eb20ab6d701f > > > https://gitbox.apache.org/repos/asf?p=nifi-maven.git;a=commit;h=d0de49a34a1197988eaa007d28e6eb20ab6d701f > > > > Checksums of nifi-nar-maven-plugin-2.0.0-source-release.zip: > > SHA256: ae889c843a82c4823fca0bf5fedf275dbb812c2b11e25ae26b0bd4ad7d26ccae > > SHA512: > > > c9afefb093d8b9568012d6697f302eb4a138f0a65a7045eaeb1bff551fb4bff23c805294700ca20984a3493eb61fe80a39d8b5b393afc85cf3f6ab1a28df831c > > > > Release artifacts are signed with the following key: > > https://people.apache.org/keys/committer/pvillard.asc > > > > KEYS file available here: > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > 5 issues were closed/resolved for this release: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354745 > > > > Release note highlights can be found here: > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiNARMavenPluginVersion2.0.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. Then please vote: > > > > [ ] +1 Release this package as nifi-nar-maven-plugin-2.0.0 > > [ ] +0 no opinion > > [ ] -1 Do not release this package because … >
Re: [VOTE] Release Apache NiFi NAR Maven Plugin 2.0.0
+1 binding - Verified everything in release helper - Built the referenced NiFi PR with the 2.0.0 plugin - Verified one of the changes for attaching the manifest xml as a build artifact Thanks Pierre! On Wed, May 22, 2024 at 7:31 AM Pierre Villard wrote: > > Hello Apache NiFi Community, > > I am pleased to be calling this vote for the source release of Apache NiFi > NAR Maven Plugin 2.0.0. This new release is intended to be used with NiFi > 2+. > > The source being voted upon, including signatures, digests, etc. can be > found at: > https://dist.apache.org/repos/dist/dev/nifi/nifi-nar-maven-plugin-2.0.0/ > > A helpful reminder on how the release candidate verification process works: > https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+NAR+Maven+Plugin+release+candidate > > Please note that when trying this release, some changes are expected on the > NiFi side as proposed in the PR: https://github.com/apache/nifi/pull/8860 > > The Git tag is nifi-maven-2.0.0-RC1 > The Git commit ID is d0de49a34a1197988eaa007d28e6eb20ab6d701f > https://gitbox.apache.org/repos/asf?p=nifi-maven.git;a=commit;h=d0de49a34a1197988eaa007d28e6eb20ab6d701f > > Checksums of nifi-nar-maven-plugin-2.0.0-source-release.zip: > SHA256: ae889c843a82c4823fca0bf5fedf275dbb812c2b11e25ae26b0bd4ad7d26ccae > SHA512: > c9afefb093d8b9568012d6697f302eb4a138f0a65a7045eaeb1bff551fb4bff23c805294700ca20984a3493eb61fe80a39d8b5b393afc85cf3f6ab1a28df831c > > Release artifacts are signed with the following key: > https://people.apache.org/keys/committer/pvillard.asc > > KEYS file available here: > https://dist.apache.org/repos/dist/release/nifi/KEYS > > 5 issues were closed/resolved for this release: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354745 > > Release note highlights can be found here: > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiNARMavenPluginVersion2.0.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. Then please vote: > > [ ] +1 Release this package as nifi-nar-maven-plugin-2.0.0 > [ ] +0 no opinion > [ ] -1 Do not release this package because …
[VOTE] Release Apache NiFi NAR Maven Plugin 2.0.0
Hello Apache NiFi Community, I am pleased to be calling this vote for the source release of Apache NiFi NAR Maven Plugin 2.0.0. This new release is intended to be used with NiFi 2+. The source being voted upon, including signatures, digests, etc. can be found at: https://dist.apache.org/repos/dist/dev/nifi/nifi-nar-maven-plugin-2.0.0/ A helpful reminder on how the release candidate verification process works: https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+NAR+Maven+Plugin+release+candidate Please note that when trying this release, some changes are expected on the NiFi side as proposed in the PR: https://github.com/apache/nifi/pull/8860 The Git tag is nifi-maven-2.0.0-RC1 The Git commit ID is d0de49a34a1197988eaa007d28e6eb20ab6d701f https://gitbox.apache.org/repos/asf?p=nifi-maven.git;a=commit;h=d0de49a34a1197988eaa007d28e6eb20ab6d701f Checksums of nifi-nar-maven-plugin-2.0.0-source-release.zip: SHA256: ae889c843a82c4823fca0bf5fedf275dbb812c2b11e25ae26b0bd4ad7d26ccae SHA512: c9afefb093d8b9568012d6697f302eb4a138f0a65a7045eaeb1bff551fb4bff23c805294700ca20984a3493eb61fe80a39d8b5b393afc85cf3f6ab1a28df831c Release artifacts are signed with the following key: https://people.apache.org/keys/committer/pvillard.asc KEYS file available here: https://dist.apache.org/repos/dist/release/nifi/KEYS 5 issues were closed/resolved for this release: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354745 Release note highlights can be found here: https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiNARMavenPluginVersion2.0.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. Then please vote: [ ] +1 Release this package as nifi-nar-maven-plugin-2.0.0 [ ] +0 no opinion [ ] -1 Do not release this package because …
Re: [DISCUSS] Release NiFi NAR Maven Plugin
Pierre, Thanks for clarifying. I agree that going to Java 21 makes sense, and aligns with the NiFi main branch. That would be a breaking change, warranting the 2.0.0 version, so that sounds like a good plan. Regards, David Handermann On Tue, May 21, 2024 at 10:32 AM Pierre Villard wrote: > > My plan was to go with the latest for everything (including Java 21). > This way, NiFi NAR Maven plugin 2.0.0 would be used only for NiFi 2.x. > I actually think that the addition of the extension type "flow analysis > rules" would break things if used in the 1.x line (unless I also update the > enum in NiFi 1.x to include flow analysis rules as an extension type but > not sure that would be a great approach). > > Le mar. 21 mai 2024 à 17:24, David Handermann > a écrit : > > > Pierre, > > > > Thanks for highlighting the differences for Flow Analysis Rules. As > > far as making this a 2.0.0 release version, do you anticipate > > including any breaking changes? > > > > The current version of the plugin is built with Java 8, so this could > > be updated to Java 21, which would be a breaking change, however, that > > should be handled before the release process. > > > > If there are no breaking changes, I recommend a version 1.6.0 release > > before a 2.0.0 release of the plugin. > > > > Regards, > > David Handermann > > > > On Tue, May 21, 2024 at 10:19 AM Pierre Villard > > wrote: > > > > > > Given that the flow analysis rules are something specific to NiFi 2, and > > > given that this is an opportunity to do some house cleaning, I'll go > > > directly to a 2.0.0 release directly and have it used only on the main > > > branch. The things that have been added as improvements are not really > > > required for 1.x anyway. > > > > > > Le mar. 21 mai 2024 à 15:40, David Handermann < > > exceptionfact...@apache.org> > > > a écrit : > > > > > > > Thanks Pierre, sounds good! > > > > > > > > Regards, > > > > David Handermann > > > > > > > > On Tue, May 21, 2024 at 8:36 AM Pierre Villard > > > > wrote: > > > > > > > > > > Thanks will go ahead with 1.6.0 release process > > > > > > > > > > Le lun. 20 mai 2024 à 19:30, Matt Burgess a > > écrit > > > > : > > > > > > > > > > > +1 for a 1.6.0 release > > > > > > > > > > > > On Mon, May 20, 2024 at 1:25 PM Bryan Bende > > wrote: > > > > > > > > > > > > > Thanks Pierre. I agree it would be good to kick out a release. I > > > > would > > > > > > > lean towards 1.6.0 since the commits seem to be improvements > > rather > > > > > > > than bug fixes for a patch. > > > > > > > > > > > > > > On Mon, May 20, 2024 at 1:08 PM Pierre Villard > > > > > > > wrote: > > > > > > > > > > > > > > > > Hi all, > > > > > > > > > > > > > > > > We just merged a couple of improvements for the NiFi NAR Maven > > > > Plugin > > > > > > and > > > > > > > > another improvement has been merged some time ago for which the > > > > > > community > > > > > > > > expressed interest [1]. I think it could be a good time to > > release > > > > a > > > > > > new > > > > > > > > version, either as 1.5.2 or as 1.6.0. Once we have a new > > release, > > > > there > > > > > > > > will be a need for updating the NiFi code base and I have a PR > > > > ready > > > > > > for > > > > > > > > that [2]. > > > > > > > > > > > > > > > > I'm happy to help with the release process. > > > > > > > > > > > > > > > > Do you agree it is time for a new release or do you see > > additional > > > > > > > changes > > > > > > > > we should make? > > > > > > > > > > > > > > > > Thanks, > > > > > > > > Pierre > > > > > > > > > > > > > > > > [1] https://github.com/apache/nifi-maven/pull/35 > > > > > > > > [2] https://issues.apache.org/jira/browse/NIFI-13267 > > > > > > > > > > > > > > > > > > >
Re: [DISCUSS] Release NiFi NAR Maven Plugin
My plan was to go with the latest for everything (including Java 21). This way, NiFi NAR Maven plugin 2.0.0 would be used only for NiFi 2.x. I actually think that the addition of the extension type "flow analysis rules" would break things if used in the 1.x line (unless I also update the enum in NiFi 1.x to include flow analysis rules as an extension type but not sure that would be a great approach). Le mar. 21 mai 2024 à 17:24, David Handermann a écrit : > Pierre, > > Thanks for highlighting the differences for Flow Analysis Rules. As > far as making this a 2.0.0 release version, do you anticipate > including any breaking changes? > > The current version of the plugin is built with Java 8, so this could > be updated to Java 21, which would be a breaking change, however, that > should be handled before the release process. > > If there are no breaking changes, I recommend a version 1.6.0 release > before a 2.0.0 release of the plugin. > > Regards, > David Handermann > > On Tue, May 21, 2024 at 10:19 AM Pierre Villard > wrote: > > > > Given that the flow analysis rules are something specific to NiFi 2, and > > given that this is an opportunity to do some house cleaning, I'll go > > directly to a 2.0.0 release directly and have it used only on the main > > branch. The things that have been added as improvements are not really > > required for 1.x anyway. > > > > Le mar. 21 mai 2024 à 15:40, David Handermann < > exceptionfact...@apache.org> > > a écrit : > > > > > Thanks Pierre, sounds good! > > > > > > Regards, > > > David Handermann > > > > > > On Tue, May 21, 2024 at 8:36 AM Pierre Villard > > > wrote: > > > > > > > > Thanks will go ahead with 1.6.0 release process > > > > > > > > Le lun. 20 mai 2024 à 19:30, Matt Burgess a > écrit > > > : > > > > > > > > > +1 for a 1.6.0 release > > > > > > > > > > On Mon, May 20, 2024 at 1:25 PM Bryan Bende > wrote: > > > > > > > > > > > Thanks Pierre. I agree it would be good to kick out a release. I > > > would > > > > > > lean towards 1.6.0 since the commits seem to be improvements > rather > > > > > > than bug fixes for a patch. > > > > > > > > > > > > On Mon, May 20, 2024 at 1:08 PM Pierre Villard > > > > > > wrote: > > > > > > > > > > > > > > Hi all, > > > > > > > > > > > > > > We just merged a couple of improvements for the NiFi NAR Maven > > > Plugin > > > > > and > > > > > > > another improvement has been merged some time ago for which the > > > > > community > > > > > > > expressed interest [1]. I think it could be a good time to > release > > > a > > > > > new > > > > > > > version, either as 1.5.2 or as 1.6.0. Once we have a new > release, > > > there > > > > > > > will be a need for updating the NiFi code base and I have a PR > > > ready > > > > > for > > > > > > > that [2]. > > > > > > > > > > > > > > I'm happy to help with the release process. > > > > > > > > > > > > > > Do you agree it is time for a new release or do you see > additional > > > > > > changes > > > > > > > we should make? > > > > > > > > > > > > > > Thanks, > > > > > > > Pierre > > > > > > > > > > > > > > [1] https://github.com/apache/nifi-maven/pull/35 > > > > > > > [2] https://issues.apache.org/jira/browse/NIFI-13267 > > > > > > > > > > > > > > >
Re: [DISCUSS] Release NiFi NAR Maven Plugin
Pierre, Thanks for highlighting the differences for Flow Analysis Rules. As far as making this a 2.0.0 release version, do you anticipate including any breaking changes? The current version of the plugin is built with Java 8, so this could be updated to Java 21, which would be a breaking change, however, that should be handled before the release process. If there are no breaking changes, I recommend a version 1.6.0 release before a 2.0.0 release of the plugin. Regards, David Handermann On Tue, May 21, 2024 at 10:19 AM Pierre Villard wrote: > > Given that the flow analysis rules are something specific to NiFi 2, and > given that this is an opportunity to do some house cleaning, I'll go > directly to a 2.0.0 release directly and have it used only on the main > branch. The things that have been added as improvements are not really > required for 1.x anyway. > > Le mar. 21 mai 2024 à 15:40, David Handermann > a écrit : > > > Thanks Pierre, sounds good! > > > > Regards, > > David Handermann > > > > On Tue, May 21, 2024 at 8:36 AM Pierre Villard > > wrote: > > > > > > Thanks will go ahead with 1.6.0 release process > > > > > > Le lun. 20 mai 2024 à 19:30, Matt Burgess a écrit > > : > > > > > > > +1 for a 1.6.0 release > > > > > > > > On Mon, May 20, 2024 at 1:25 PM Bryan Bende wrote: > > > > > > > > > Thanks Pierre. I agree it would be good to kick out a release. I > > would > > > > > lean towards 1.6.0 since the commits seem to be improvements rather > > > > > than bug fixes for a patch. > > > > > > > > > > On Mon, May 20, 2024 at 1:08 PM Pierre Villard > > > > > wrote: > > > > > > > > > > > > Hi all, > > > > > > > > > > > > We just merged a couple of improvements for the NiFi NAR Maven > > Plugin > > > > and > > > > > > another improvement has been merged some time ago for which the > > > > community > > > > > > expressed interest [1]. I think it could be a good time to release > > a > > > > new > > > > > > version, either as 1.5.2 or as 1.6.0. Once we have a new release, > > there > > > > > > will be a need for updating the NiFi code base and I have a PR > > ready > > > > for > > > > > > that [2]. > > > > > > > > > > > > I'm happy to help with the release process. > > > > > > > > > > > > Do you agree it is time for a new release or do you see additional > > > > > changes > > > > > > we should make? > > > > > > > > > > > > Thanks, > > > > > > Pierre > > > > > > > > > > > > [1] https://github.com/apache/nifi-maven/pull/35 > > > > > > [2] https://issues.apache.org/jira/browse/NIFI-13267 > > > > > > > > > > >
Re: [DISCUSS] Release NiFi NAR Maven Plugin
Given that the flow analysis rules are something specific to NiFi 2, and given that this is an opportunity to do some house cleaning, I'll go directly to a 2.0.0 release directly and have it used only on the main branch. The things that have been added as improvements are not really required for 1.x anyway. Le mar. 21 mai 2024 à 15:40, David Handermann a écrit : > Thanks Pierre, sounds good! > > Regards, > David Handermann > > On Tue, May 21, 2024 at 8:36 AM Pierre Villard > wrote: > > > > Thanks will go ahead with 1.6.0 release process > > > > Le lun. 20 mai 2024 à 19:30, Matt Burgess a écrit > : > > > > > +1 for a 1.6.0 release > > > > > > On Mon, May 20, 2024 at 1:25 PM Bryan Bende wrote: > > > > > > > Thanks Pierre. I agree it would be good to kick out a release. I > would > > > > lean towards 1.6.0 since the commits seem to be improvements rather > > > > than bug fixes for a patch. > > > > > > > > On Mon, May 20, 2024 at 1:08 PM Pierre Villard > > > > wrote: > > > > > > > > > > Hi all, > > > > > > > > > > We just merged a couple of improvements for the NiFi NAR Maven > Plugin > > > and > > > > > another improvement has been merged some time ago for which the > > > community > > > > > expressed interest [1]. I think it could be a good time to release > a > > > new > > > > > version, either as 1.5.2 or as 1.6.0. Once we have a new release, > there > > > > > will be a need for updating the NiFi code base and I have a PR > ready > > > for > > > > > that [2]. > > > > > > > > > > I'm happy to help with the release process. > > > > > > > > > > Do you agree it is time for a new release or do you see additional > > > > changes > > > > > we should make? > > > > > > > > > > Thanks, > > > > > Pierre > > > > > > > > > > [1] https://github.com/apache/nifi-maven/pull/35 > > > > > [2] https://issues.apache.org/jira/browse/NIFI-13267 > > > > > > > >
Re: [DISCUSS] Release NiFi NAR Maven Plugin
Thanks Pierre, sounds good! Regards, David Handermann On Tue, May 21, 2024 at 8:36 AM Pierre Villard wrote: > > Thanks will go ahead with 1.6.0 release process > > Le lun. 20 mai 2024 à 19:30, Matt Burgess a écrit : > > > +1 for a 1.6.0 release > > > > On Mon, May 20, 2024 at 1:25 PM Bryan Bende wrote: > > > > > Thanks Pierre. I agree it would be good to kick out a release. I would > > > lean towards 1.6.0 since the commits seem to be improvements rather > > > than bug fixes for a patch. > > > > > > On Mon, May 20, 2024 at 1:08 PM Pierre Villard > > > wrote: > > > > > > > > Hi all, > > > > > > > > We just merged a couple of improvements for the NiFi NAR Maven Plugin > > and > > > > another improvement has been merged some time ago for which the > > community > > > > expressed interest [1]. I think it could be a good time to release a > > new > > > > version, either as 1.5.2 or as 1.6.0. Once we have a new release, there > > > > will be a need for updating the NiFi code base and I have a PR ready > > for > > > > that [2]. > > > > > > > > I'm happy to help with the release process. > > > > > > > > Do you agree it is time for a new release or do you see additional > > > changes > > > > we should make? > > > > > > > > Thanks, > > > > Pierre > > > > > > > > [1] https://github.com/apache/nifi-maven/pull/35 > > > > [2] https://issues.apache.org/jira/browse/NIFI-13267 > > > > >
Re: [DISCUSS] Release NiFi NAR Maven Plugin
Thanks will go ahead with 1.6.0 release process Le lun. 20 mai 2024 à 19:30, Matt Burgess a écrit : > +1 for a 1.6.0 release > > On Mon, May 20, 2024 at 1:25 PM Bryan Bende wrote: > > > Thanks Pierre. I agree it would be good to kick out a release. I would > > lean towards 1.6.0 since the commits seem to be improvements rather > > than bug fixes for a patch. > > > > On Mon, May 20, 2024 at 1:08 PM Pierre Villard > > wrote: > > > > > > Hi all, > > > > > > We just merged a couple of improvements for the NiFi NAR Maven Plugin > and > > > another improvement has been merged some time ago for which the > community > > > expressed interest [1]. I think it could be a good time to release a > new > > > version, either as 1.5.2 or as 1.6.0. Once we have a new release, there > > > will be a need for updating the NiFi code base and I have a PR ready > for > > > that [2]. > > > > > > I'm happy to help with the release process. > > > > > > Do you agree it is time for a new release or do you see additional > > changes > > > we should make? > > > > > > Thanks, > > > Pierre > > > > > > [1] https://github.com/apache/nifi-maven/pull/35 > > > [2] https://issues.apache.org/jira/browse/NIFI-13267 > > >
Re: [DISCUSS] Release NiFi NAR Maven Plugin
+1 for a 1.6.0 release On Mon, May 20, 2024 at 1:25 PM Bryan Bende wrote: > Thanks Pierre. I agree it would be good to kick out a release. I would > lean towards 1.6.0 since the commits seem to be improvements rather > than bug fixes for a patch. > > On Mon, May 20, 2024 at 1:08 PM Pierre Villard > wrote: > > > > Hi all, > > > > We just merged a couple of improvements for the NiFi NAR Maven Plugin and > > another improvement has been merged some time ago for which the community > > expressed interest [1]. I think it could be a good time to release a new > > version, either as 1.5.2 or as 1.6.0. Once we have a new release, there > > will be a need for updating the NiFi code base and I have a PR ready for > > that [2]. > > > > I'm happy to help with the release process. > > > > Do you agree it is time for a new release or do you see additional > changes > > we should make? > > > > Thanks, > > Pierre > > > > [1] https://github.com/apache/nifi-maven/pull/35 > > [2] https://issues.apache.org/jira/browse/NIFI-13267 >
Re: [DISCUSS] Release NiFi NAR Maven Plugin
Thanks Pierre. I agree it would be good to kick out a release. I would lean towards 1.6.0 since the commits seem to be improvements rather than bug fixes for a patch. On Mon, May 20, 2024 at 1:08 PM Pierre Villard wrote: > > Hi all, > > We just merged a couple of improvements for the NiFi NAR Maven Plugin and > another improvement has been merged some time ago for which the community > expressed interest [1]. I think it could be a good time to release a new > version, either as 1.5.2 or as 1.6.0. Once we have a new release, there > will be a need for updating the NiFi code base and I have a PR ready for > that [2]. > > I'm happy to help with the release process. > > Do you agree it is time for a new release or do you see additional changes > we should make? > > Thanks, > Pierre > > [1] https://github.com/apache/nifi-maven/pull/35 > [2] https://issues.apache.org/jira/browse/NIFI-13267
[DISCUSS] Release NiFi NAR Maven Plugin
Hi all, We just merged a couple of improvements for the NiFi NAR Maven Plugin and another improvement has been merged some time ago for which the community expressed interest [1]. I think it could be a good time to release a new version, either as 1.5.2 or as 1.6.0. Once we have a new release, there will be a need for updating the NiFi code base and I have a PR ready for that [2]. I'm happy to help with the release process. Do you agree it is time for a new release or do you see additional changes we should make? Thanks, Pierre [1] https://github.com/apache/nifi-maven/pull/35 [2] https://issues.apache.org/jira/browse/NIFI-13267
[ANNOUNCE] Apache NiFi MiNiFi C++ 0.99.0 release
Hello The Apache NiFi team would like to announce the release of Apache NiFi MiNiFi C++ 0.99.0. New features in this release: Added support for using NiFi 2.0 Python processors in MiNiFi C++ Added new python based multiplatform bootstrap script Added encryption support for sensitive properties in flow configuration Releasing Windows installer now can be done (and will be done) under the Apache license Added support for service installation on MacOS Added C2 debug command to MiNiFi Controller Added support for setting MiNiFi properties from command line Added system load average field to C2 and Prometheus metrics Added support for manually configuring RocksDB options Added custom delimiter property for ListenTCP processor Added bandwidth limit properties to InvokeHTTP processor Added JSON flow configuration examples New processors: Added PutSmb, FetchSmb and ListSmb processor for SMB networking protocol support Added PushGrafanaLokiGrpc and PushGrafanaLokiREST processors for pushing logs to Grafana Loki Added JoltTransform to use Jolt JSON transformations Added SplitText processor Added AttributeRollingWindow processor Changes and improvements: Dropped support for disabling peer verification in InvokeHTTP Corrupt flow files are now filtered to avoid errors in the flow Using administrative yield duration instead of onschedule retry interval in scheduling adjusting to NiFi's functionality Fixed high disk IO usage issue with MergeContent Fixed the site-to-site transfer or large files Fixed memory leak caused by unused loggers Fixed yielding processors to still respect scheduling period Upgraded dependencies: Upgraded OpenSSL to version 3.3.0 Upgraded AWS SDK to version 1.11.219 with support for new AWS regions Upgraded libuvc to version 0.0.7 Upgraded docker base image to alpine:3.18 Upgraded Sol2 to version 3.3.0 MiNiFi—a subproject of Apache NiFi—is a complementary data collection approach that supplements the core tenets of NiFi in dataflow management, focusing on the collection of data at the source of its creation. Specific goals for the initial thrust of the MiNiFi effort comprise: Small size and low resource consumption Central management of agents Generation of data provenance (full chain of custody of information) Integration with NiFi for follow-on dataflow management More details on Apache NiFi MiNiFi can be found here: https://nifi.apache.org/minifi The release artifacts can be downloaded from here: https://nifi.apache.org/download/ Issues closed/resolved for this list can be found here: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321520=12353618 Release note highlights can be found here: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65145325#ReleaseNotesMiNiFi(C++)-Versioncpp-0.99.0 Thank you The Apache NiFi team
[RESULT][VOTE] Release Apache NiFi MiNiFi C++ 0.99.0
Apache NiFi Community, I am pleased to announce that the 0.99.0 release of Apache NiFi MiNiFi C++ passes with 3 +1 (binding) votes 3 +1 (non-binding) votes 0 0 votes 0 -1 votes Thanks to all who helped make this release possible! The release artifacts will be published in the next 24 hours. Here is the PMC vote thread: https://lists.apache.org/thread/ox6bg1l278yqwcp2htwmrs1y3jw1jmzs Thanks, Gabor
Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.99.0 (RC4)
+1 binding. Source builds now on osx. usual checks for license/notice good. Checks on signature/hashes/latest commit all good. Wasn't able to 'make docker' successfully but likely a local config issue. On Thu, May 16, 2024 at 11:10 AM Pierre Villard wrote: > +1 (binding) > > Went through the usual steps > Built on MacOS X. > Tested a basic flow tailing a local file, doing some transformations and > sending data with InvokeHTTP to a NiFi instance with FlowFile format. > > Thanks team for taking care of this release and the exciting upcoming 1.0. > > Le mer. 15 mai 2024 à 17:30, Ferenc Gerlits a écrit > : > > > +1 (non-binding) > > > > verified signature and hashes > > installed the Windows MSI and ran the service on Windows > > compiled on Fedora 40 and ran ExecuteScript with lua > > > > It mostly worked as expected. I found two minor issues: > > https://issues.apache.org/jira/browse/MINIFICPP-2374, > > https://issues.apache.org/jira/browse/MINIFICPP-2375, but neither of > > these is a showstopper, we'll fix them in the next release. > > > > Thank you for RMing! > > Ferenc > > >
[ANNOUNCE] Apache NiFi 2.0.0-M3 Released
The Apache NiFi Team is pleased to announce the release of Apache NiFi 2.0.0-M3. Apache NiFi is an easy to use, powerful, and reliable system to process and distribute data. https://nifi.apache.org The release artifacts can be downloaded from the project website. https://nifi.apache.org/download/ Maven artifacts have been released and mirrored according to ASF artifact distribution processes. Issues resolved in Apache NiFi 2.0.0-M3 are listed in Jira Release Notes. https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354155 Highlights of the release are available on the project wiki page: https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0-M3 Thank you, The Apache NiFi Team
[RESULT][VOTE] Release Apache NiFi 2.0.0-M3 (RC1)
Apache NiFi Community, I am pleased to announce that the 2.0.0-M3 release of Apache NiFi passes: 9 +1 (binding) votes 10 +1 (non-binding) votes 0 0 votes 0 -1 votes Thanks to all who helped make this release possible! The release artifacts will be published in the next 24 hours. Here is the vote thread: https://lists.apache.org/thread/ocxc43gklt2qb36n6wxjp0x868bq71gq
Re: [VOTE] Release Apache NiFi 2.0.0-M3 (RC1)
+1 binding On Mon, May 13, 2024 at 10:48 PM David Handermann wrote: > > Team, > > I am pleased to be calling this vote for the source release of Apache > NiFi 2.0.0-M3. > > Please review the following guide for how to verify a release candidate build: > > https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification > > The source being voted on and the convenience binaries are available > on the Apache Distribution Repository: > > https://dist.apache.org/repos/dist/dev/nifi/nifi-2.0.0-M3 > > The build artifacts are available on the Apache Nexus Repository: > > https://repository.apache.org/content/repositories/orgapachenifi-1269 > > Git Tag: nifi-2.0.0-M3-RC1 > Git Commit ID: f2215c6522a5571189290760c55f0317f8562cbd > GitHub Commit Link: > https://github.com/apache/nifi/commit/f2215c6522a5571189290760c55f0317f8562cbd > > Checksums of nifi-2.0.0-M3-source-release.zip > > SHA256: d471a0a9e4e04faf13bbe13c7d83be6f8002fba598bf0968a3c1b339802a185a > SHA512: > cd0b8bbd3fe4ea7ebe8cdac6ac8a7afa97fd7b6a521c2cbcb2c0cdc94899b652bf3726c8fe432e16f44a9dc81907414bbb42e03113f0cd9fb51aa1de9cd727a7 > > Release artifacts are signed with the following key: > > https://people.apache.org/keys/committer/exceptionfactory.asc > > KEYS file is available on the Apache Distribution Repository: > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > Issues resolved for this version: 411 > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354155 > > Release note highlights can be found on the project wiki: > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0-M3 > > 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. > Then please vote: > > [] +1 Release this package as nifi-2.0.0-M3 > [] +0 no opinion > [] -1 Do not release this package because...
Re: [VOTE] Release Apache NiFi 2.0.0-M3 (RC1)
+1 (non-binding) - Verified hashes and signatures - Successfully built NiFi 2.0.0-M3 with contrib-check in the following environment: - Maven: 3.9.6 - Java 21.0.3 openjdk - Red Hat, Inc I did notice some non showstoppers such as discrepancies in the NOTICE file which should be addressed in NIFI-13253 <https://issues.apache.org/jira/browse/NIFI-13253> and various uses of deprecated API features which should be addressed in NIFI-13250, NIFI-13251, NIFI-13252, NIFI-13254 and NIFI-13255. Thank you David for RMing! On Thu, May 16, 2024 at 2:25 PM Pierre Villard wrote: > +1 (binding) > > Went through the usual steps, deployed a secured cluster with a secured > NiFi Registry instance on GCP and tested a bunch of flows that I have > around. > > Thanks for RM'ing David! > > > Le jeu. 16 mai 2024 à 15:26, Matt Burgess a écrit : > > > +1 (binding) > > > > Ran through release helper, verified various flows. Thanks for RM'ing > > David! > > > > On Mon, May 13, 2024 at 11:48 PM David Handermann < > > exceptionfact...@apache.org> wrote: > > > > > Team, > > > > > > I am pleased to be calling this vote for the source release of Apache > > > NiFi 2.0.0-M3. > > > > > > Please review the following guide for how to verify a release candidate > > > build: > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification > > > > > > The source being voted on and the convenience binaries are available > > > on the Apache Distribution Repository: > > > > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-2.0.0-M3 > > > > > > The build artifacts are available on the Apache Nexus Repository: > > > > > > https://repository.apache.org/content/repositories/orgapachenifi-1269 > > > > > > Git Tag: nifi-2.0.0-M3-RC1 > > > Git Commit ID: f2215c6522a5571189290760c55f0317f8562cbd > > > GitHub Commit Link: > > > > > > > > > https://github.com/apache/nifi/commit/f2215c6522a5571189290760c55f0317f8562cbd > > > > > > Checksums of nifi-2.0.0-M3-source-release.zip > > > > > > SHA256: > d471a0a9e4e04faf13bbe13c7d83be6f8002fba598bf0968a3c1b339802a185a > > > SHA512: > > > > > > cd0b8bbd3fe4ea7ebe8cdac6ac8a7afa97fd7b6a521c2cbcb2c0cdc94899b652bf3726c8fe432e16f44a9dc81907414bbb42e03113f0cd9fb51aa1de9cd727a7 > > > > > > Release artifacts are signed with the following key: > > > > > > https://people.apache.org/keys/committer/exceptionfactory.asc > > > > > > KEYS file is available on the Apache Distribution Repository: > > > > > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > > > Issues resolved for this version: 411 > > > > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354155 > > > > > > Release note highlights can be found on the project wiki: > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0-M3 > > > > > > 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. > > > Then please vote: > > > > > > [] +1 Release this package as nifi-2.0.0-M3 > > > [] +0 no opinion > > > [] -1 Do not release this package because... > > > > > >
Re: [VOTE] Release Apache NiFi 2.0.0-M3 (RC1)
+1 (binding) Stepped through the release helper to verify the things. Apache Maven 3.9.6 Java version: 21.0.3 Red Hat Enterprise Linux 8.9 Upgraded NiFi from 2.0.0-M2 to 2.0.0-M3. Upgraded NiFi Registry from 2.0.0-M2 to 2.0.0-M3 Tested a few flows with no problems. -- Mike On Thu, May 16, 2024 at 2:25 PM Pierre Villard wrote: > +1 (binding) > > Went through the usual steps, deployed a secured cluster with a secured > NiFi Registry instance on GCP and tested a bunch of flows that I have > around. > > Thanks for RM'ing David! > > > Le jeu. 16 mai 2024 à 15:26, Matt Burgess a écrit : > > > +1 (binding) > > > > Ran through release helper, verified various flows. Thanks for RM'ing > > David! > > > > On Mon, May 13, 2024 at 11:48 PM David Handermann < > > exceptionfact...@apache.org> wrote: > > > > > Team, > > > > > > I am pleased to be calling this vote for the source release of Apache > > > NiFi 2.0.0-M3. > > > > > > Please review the following guide for how to verify a release candidate > > > build: > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification > > > > > > The source being voted on and the convenience binaries are available > > > on the Apache Distribution Repository: > > > > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-2.0.0-M3 > > > > > > The build artifacts are available on the Apache Nexus Repository: > > > > > > https://repository.apache.org/content/repositories/orgapachenifi-1269 > > > > > > Git Tag: nifi-2.0.0-M3-RC1 > > > Git Commit ID: f2215c6522a5571189290760c55f0317f8562cbd > > > GitHub Commit Link: > > > > > > > > > https://github.com/apache/nifi/commit/f2215c6522a5571189290760c55f0317f8562cbd > > > > > > Checksums of nifi-2.0.0-M3-source-release.zip > > > > > > SHA256: > d471a0a9e4e04faf13bbe13c7d83be6f8002fba598bf0968a3c1b339802a185a > > > SHA512: > > > > > > cd0b8bbd3fe4ea7ebe8cdac6ac8a7afa97fd7b6a521c2cbcb2c0cdc94899b652bf3726c8fe432e16f44a9dc81907414bbb42e03113f0cd9fb51aa1de9cd727a7 > > > > > > Release artifacts are signed with the following key: > > > > > > https://people.apache.org/keys/committer/exceptionfactory.asc > > > > > > KEYS file is available on the Apache Distribution Repository: > > > > > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > > > Issues resolved for this version: 411 > > > > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354155 > > > > > > Release note highlights can be found on the project wiki: > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0-M3 > > > > > > 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. > > > Then please vote: > > > > > > [] +1 Release this package as nifi-2.0.0-M3 > > > [] +0 no opinion > > > [] -1 Do not release this package because... > > > > > >
Re: [VOTE] Release Apache NiFi 2.0.0-M3 (RC1)
+1 (binding) Went through the usual steps, deployed a secured cluster with a secured NiFi Registry instance on GCP and tested a bunch of flows that I have around. Thanks for RM'ing David! Le jeu. 16 mai 2024 à 15:26, Matt Burgess a écrit : > +1 (binding) > > Ran through release helper, verified various flows. Thanks for RM'ing > David! > > On Mon, May 13, 2024 at 11:48 PM David Handermann < > exceptionfact...@apache.org> wrote: > > > Team, > > > > I am pleased to be calling this vote for the source release of Apache > > NiFi 2.0.0-M3. > > > > Please review the following guide for how to verify a release candidate > > build: > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification > > > > The source being voted on and the convenience binaries are available > > on the Apache Distribution Repository: > > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-2.0.0-M3 > > > > The build artifacts are available on the Apache Nexus Repository: > > > > https://repository.apache.org/content/repositories/orgapachenifi-1269 > > > > Git Tag: nifi-2.0.0-M3-RC1 > > Git Commit ID: f2215c6522a5571189290760c55f0317f8562cbd > > GitHub Commit Link: > > > > > https://github.com/apache/nifi/commit/f2215c6522a5571189290760c55f0317f8562cbd > > > > Checksums of nifi-2.0.0-M3-source-release.zip > > > > SHA256: d471a0a9e4e04faf13bbe13c7d83be6f8002fba598bf0968a3c1b339802a185a > > SHA512: > > > cd0b8bbd3fe4ea7ebe8cdac6ac8a7afa97fd7b6a521c2cbcb2c0cdc94899b652bf3726c8fe432e16f44a9dc81907414bbb42e03113f0cd9fb51aa1de9cd727a7 > > > > Release artifacts are signed with the following key: > > > > https://people.apache.org/keys/committer/exceptionfactory.asc > > > > KEYS file is available on the Apache Distribution Repository: > > > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > Issues resolved for this version: 411 > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354155 > > > > Release note highlights can be found on the project wiki: > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0-M3 > > > > 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. > > Then please vote: > > > > [] +1 Release this package as nifi-2.0.0-M3 > > [] +0 no opinion > > [] -1 Do not release this package because... > > >
Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.99.0 (RC4)
+1 (binding) Went through the usual steps Built on MacOS X. Tested a basic flow tailing a local file, doing some transformations and sending data with InvokeHTTP to a NiFi instance with FlowFile format. Thanks team for taking care of this release and the exciting upcoming 1.0. Le mer. 15 mai 2024 à 17:30, Ferenc Gerlits a écrit : > +1 (non-binding) > > verified signature and hashes > installed the Windows MSI and ran the service on Windows > compiled on Fedora 40 and ran ExecuteScript with lua > > It mostly worked as expected. I found two minor issues: > https://issues.apache.org/jira/browse/MINIFICPP-2374, > https://issues.apache.org/jira/browse/MINIFICPP-2375, but neither of > these is a showstopper, we'll fix them in the next release. > > Thank you for RMing! > Ferenc >
Re: Inquiry Regarding Missing Documentation for selectHive3QL in nifi-hive3-nar for NiFi 1.25.0
Hello Mat, Is it packaged with NiFi 2? Documentation [1]for NiFi 2 has it 1. https://nifi.apache.org/documentation/nifi-2.0.0-M2/components/org.apache.nifi/nifi-hive3-nar/2.0.0-M2/org.apache.nifi.processors.hive.SelectHive3QL/index.html On Thu, 16 May 2024 at 16:12, Matt Burgess wrote: > Jing, > > Because SelectHive3QL (and the nifi-hive3-nar in general) is not included > with the convenience binary for Apache NiFi, the documentation for it is > not published on the website. If you downloaded and installed the NAR into > your instance, the documentation is available by dragging a SelectHive3QL > instance onto the canvas, right-clicking on it and choosing "View usage" or > "View documentation". > > Regards, > Matt > > > On Wed, May 15, 2024 at 12:10 AM yetong gao wrote: > > > Dear NiFi Development Team, > > > > I hope this message finds you well. I am currently working with Apache > NiFi > > 1.25.0 and it's already operational in our data processing pipeline. In > my > > research, I've noticed a scarcity of documentation regarding the > > selectHive3QL processor, specifically on the official NiFi documentation > > website. > > > > I'd greatly appreciate any information you could provide on why the > > selectHive3QL processor's documentation is not available on the NiFi > > website, or if there are plans to include it in the future. > > > > I believe comprehensive documentation for each processor in NiFi is > > essential for users to maximise the potential of this powerful platform. > > > > I look forward to your response. Thank you in advance. > > > > Best Regard, > > Jing > > >
Re: [VOTE] Release Apache NiFi 2.0.0-M3 (RC1)
+1 (binding) Ran through release helper, verified various flows. Thanks for RM'ing David! On Mon, May 13, 2024 at 11:48 PM David Handermann < exceptionfact...@apache.org> wrote: > Team, > > I am pleased to be calling this vote for the source release of Apache > NiFi 2.0.0-M3. > > Please review the following guide for how to verify a release candidate > build: > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification > > The source being voted on and the convenience binaries are available > on the Apache Distribution Repository: > > https://dist.apache.org/repos/dist/dev/nifi/nifi-2.0.0-M3 > > The build artifacts are available on the Apache Nexus Repository: > > https://repository.apache.org/content/repositories/orgapachenifi-1269 > > Git Tag: nifi-2.0.0-M3-RC1 > Git Commit ID: f2215c6522a5571189290760c55f0317f8562cbd > GitHub Commit Link: > > https://github.com/apache/nifi/commit/f2215c6522a5571189290760c55f0317f8562cbd > > Checksums of nifi-2.0.0-M3-source-release.zip > > SHA256: d471a0a9e4e04faf13bbe13c7d83be6f8002fba598bf0968a3c1b339802a185a > SHA512: > cd0b8bbd3fe4ea7ebe8cdac6ac8a7afa97fd7b6a521c2cbcb2c0cdc94899b652bf3726c8fe432e16f44a9dc81907414bbb42e03113f0cd9fb51aa1de9cd727a7 > > Release artifacts are signed with the following key: > > https://people.apache.org/keys/committer/exceptionfactory.asc > > KEYS file is available on the Apache Distribution Repository: > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > Issues resolved for this version: 411 > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354155 > > Release note highlights can be found on the project wiki: > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0-M3 > > 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. > Then please vote: > > [] +1 Release this package as nifi-2.0.0-M3 > [] +0 no opinion > [] -1 Do not release this package because... >
Re: Inquiry Regarding Missing Documentation for selectHive3QL in nifi-hive3-nar for NiFi 1.25.0
Jing, Because SelectHive3QL (and the nifi-hive3-nar in general) is not included with the convenience binary for Apache NiFi, the documentation for it is not published on the website. If you downloaded and installed the NAR into your instance, the documentation is available by dragging a SelectHive3QL instance onto the canvas, right-clicking on it and choosing "View usage" or "View documentation". Regards, Matt On Wed, May 15, 2024 at 12:10 AM yetong gao wrote: > Dear NiFi Development Team, > > I hope this message finds you well. I am currently working with Apache NiFi > 1.25.0 and it's already operational in our data processing pipeline. In my > research, I've noticed a scarcity of documentation regarding the > selectHive3QL processor, specifically on the official NiFi documentation > website. > > I'd greatly appreciate any information you could provide on why the > selectHive3QL processor's documentation is not available on the NiFi > website, or if there are plans to include it in the future. > > I believe comprehensive documentation for each processor in NiFi is > essential for users to maximise the potential of this powerful platform. > > I look forward to your response. Thank you in advance. > > Best Regard, > Jing >
Re: [VOTE] Release Apache NiFi 2.0.0-M3 (RC1)
+1 (non-binding) - Verified hashes and signatures - Successfully built NiFi 2.0.0-M3 with contrib-check in the following environment: - Ubuntu 22.04 6.5.0-35-generic - java 21 2023-09-19 LTS - Apache Maven 3.9.6 - Designed and ran a simple flow with S3 upload - Tested python extension using a flow with PromptChatGPT processor - Tested S2S communication and HTTP data forwarding from MiNiFi C++ Thanks David for RMing! Regards, Gabor On Thu, 16 May 2024 at 13:12, Marton Szasz wrote: > +1 (binding) > > Followed the usual steps, compiled and tested NiFi in this environment > (Ubuntu 24.04): > Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae) > Maven home: /home/szaszm/apache-maven-3.9.6 > Java version: 21.0.3, vendor: Ubuntu, runtime: > /usr/lib/jvm/java-21-openjdk-amd64 > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "6.8.0-31-generic", arch: "amd64", family: > "unix" > > Tested receiving logs from minifi c++ through HTTP, and decompressing them. > > Thanks for the release, David! > > Marton > > On 5/16/24 11:09 AM, Márk Báthori wrote: > > +1 (non-binding) > > > > - went through the helper guide, > > - did a full build with contrib check > > - verified signatures and hashes > > > > Environment: > > - macOS Version 14.3.1 > > - OpenJDK Runtime Environment Zulu21.28+85-CA (build 21+35) > > - Apache Maven 3.9.6 > > > > Created and ran some simple flows. > > > > Thanks for RMing David! > > > > Regards, > > Mark > > > > Krisztina Zsihovszki ezt írta (időpont: 2024. máj. > > 16., Cs, 10:40): > > > >> +1 (non-binding) > >> > >> - Verified signatures and hashes > >> - Ran build using Maven 3.9.5 on macOS 13.5 with Java 21-zulu (build > 21+35) > >> - Contrib check, unit tests passed > >> > >> Verified these tickets: > >> > >> [NIFI-13146] - ConsumeSlack processor rate limited > >> [NIFI-12732] - ListS3 should reset its tracking state after > configuration > >> change > >> > >> Thanks for RMing, David! > >> > >> On Thu, May 16, 2024 at 9:27 AM Ferenc Kis > >> wrote: > >> > >>> +1 (non-binding) > >>> > >>> Went through the helper guide, local maven repo cleaned up, full clean > >>> build with contrib check, verified signatures and hashes > >>> > >>> Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae) > >>> Maven home: /Users/fkis/.sdkman/candidates/maven/current > >>> Java version: 21.0.3, vendor: Azul Systems, Inc., runtime: > >>> > /Users/fkis/.sdkman/candidates/java/21.0.3-zulu/zulu-21.jdk/Contents/Home > >>> Default locale: en_HU, platform encoding: UTF-8 > >>> OS name: "mac os x", version: "14.4.1", arch: "aarch64", family: "mac" > >>> > >>> Validations performed: > >>> - Started NiFi, created a simple flow with ListenHTTP and Input Port. > >>> Validated ListenHTTP processor is able to receive data > >>> - Started MiNiFi Java: > >>>* created a simple GenerateFlowFile -> InvokeHttp flow and > >>> GenerateFlowFile -> RemoteProcessGroup flow and pushed to MiNiFi via C2 > >>> protocol > >>>* Validated that connectivity between NiFi and MiNiFi works via both > >>> InvokeHTTP and S2S > >>> - NIFI-13019 ClassNotFoundException when using HandleHttpRequest in > >>> MiNiFi-2.0.0-M2 > >>> - NIFI-13123 [MiNiFi] Async C2 Operation Queue > >>> > >>> Thanks for RMing David! > >>> > >>> Regards > >>> Ferenc > >>> > >>> On Thu, May 16, 2024 at 3:44 AM Csaba Bejan > >> wrote: > >>>> +1 (binding) > >>>> > >>>> - Went through the helper guide and did a clean build > >>>> - Verified signatures and hashes > >>>> - Built on OSX 14.2.1 > >>>> - Java version: Zulu21.28+85-CA (build 21+35) > >>>> - Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546) > >>>> - Started NiFi and created a simple flow > >>>> - Started MiNiFi and verified integration with C2 Server. Played > >>> around > >>>> with the C2 protocol (Operations - Update, Transfer, Describe...) > >>>> > >>>> Verified: > >>>> > >>>> - NIF
Re: [VOTE] Release Apache NiFi 2.0.0-M3 (RC1)
+1 (binding)
Followed the usual steps, compiled and tested NiFi in this environment
(Ubuntu 24.04):
Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
Maven home: /home/szaszm/apache-maven-3.9.6
Java version: 21.0.3, vendor: Ubuntu, runtime:
/usr/lib/jvm/java-21-openjdk-amd64
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "6.8.0-31-generic", arch: "amd64", family: "unix"
Tested receiving logs from minifi c++ through HTTP, and decompressing them.
Thanks for the release, David!
Marton
On 5/16/24 11:09 AM, Márk Báthori wrote:
+1 (non-binding)
- went through the helper guide,
- did a full build with contrib check
- verified signatures and hashes
Environment:
- macOS Version 14.3.1
- OpenJDK Runtime Environment Zulu21.28+85-CA (build 21+35)
- Apache Maven 3.9.6
Created and ran some simple flows.
Thanks for RMing David!
Regards,
Mark
Krisztina Zsihovszki ezt írta (időpont: 2024. máj.
16., Cs, 10:40):
+1 (non-binding)
- Verified signatures and hashes
- Ran build using Maven 3.9.5 on macOS 13.5 with Java 21-zulu (build 21+35)
- Contrib check, unit tests passed
Verified these tickets:
[NIFI-13146] - ConsumeSlack processor rate limited
[NIFI-12732] - ListS3 should reset its tracking state after configuration
change
Thanks for RMing, David!
On Thu, May 16, 2024 at 9:27 AM Ferenc Kis
wrote:
+1 (non-binding)
Went through the helper guide, local maven repo cleaned up, full clean
build with contrib check, verified signatures and hashes
Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
Maven home: /Users/fkis/.sdkman/candidates/maven/current
Java version: 21.0.3, vendor: Azul Systems, Inc., runtime:
/Users/fkis/.sdkman/candidates/java/21.0.3-zulu/zulu-21.jdk/Contents/Home
Default locale: en_HU, platform encoding: UTF-8
OS name: "mac os x", version: "14.4.1", arch: "aarch64", family: "mac"
Validations performed:
- Started NiFi, created a simple flow with ListenHTTP and Input Port.
Validated ListenHTTP processor is able to receive data
- Started MiNiFi Java:
* created a simple GenerateFlowFile -> InvokeHttp flow and
GenerateFlowFile -> RemoteProcessGroup flow and pushed to MiNiFi via C2
protocol
* Validated that connectivity between NiFi and MiNiFi works via both
InvokeHTTP and S2S
- NIFI-13019 ClassNotFoundException when using HandleHttpRequest in
MiNiFi-2.0.0-M2
- NIFI-13123 [MiNiFi] Async C2 Operation Queue
Thanks for RMing David!
Regards
Ferenc
On Thu, May 16, 2024 at 3:44 AM Csaba Bejan
wrote:
+1 (binding)
- Went through the helper guide and did a clean build
- Verified signatures and hashes
- Built on OSX 14.2.1
- Java version: Zulu21.28+85-CA (build 21+35)
- Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546)
- Started NiFi and created a simple flow
- Started MiNiFi and verified integration with C2 Server. Played
around
with the C2 protocol (Operations - Update, Transfer, Describe...)
Verified:
- NIFI-13123 [MiNiFi] Async C2 Operation Queue
- NIFI-13019 ClassNotFoundException when using HandleHttpRequest in
MiNiFi-2.0.0-M2
Thanks for RMing, David!
Regards,
Csaba
On Mon, May 13, 2024 at 11:49 PM David Handermann <
exceptionfact...@apache.org> wrote:
Team,
I am pleased to be calling this vote for the source release of Apache
NiFi 2.0.0-M3.
Please review the following guide for how to verify a release
candidate
build:
https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification
The source being voted on and the convenience binaries are available
on the Apache Distribution Repository:
https://dist.apache.org/repos/dist/dev/nifi/nifi-2.0.0-M3
The build artifacts are available on the Apache Nexus Repository:
https://repository.apache.org/content/repositories/orgapachenifi-1269
Git Tag: nifi-2.0.0-M3-RC1
Git Commit ID: f2215c6522a5571189290760c55f0317f8562cbd
GitHub Commit Link:
https://github.com/apache/nifi/commit/f2215c6522a5571189290760c55f0317f8562cbd
Checksums of nifi-2.0.0-M3-source-release.zip
SHA256:
d471a0a9e4e04faf13bbe13c7d83be6f8002fba598bf0968a3c1b339802a185a
SHA512:
cd0b8bbd3fe4ea7ebe8cdac6ac8a7afa97fd7b6a521c2cbcb2c0cdc94899b652bf3726c8fe432e16f44a9dc81907414bbb42e03113f0cd9fb51aa1de9cd727a7
Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/exceptionfactory.asc
KEYS file is available on the Apache Distribution Repository:
https://dist.apache.org/repos/dist/release/nifi/KEYS
Issues resolved for this version: 411
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354155
Release note highlights can be found on the project wiki:
https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0-M3
The vote will be open for 72 hours.
Please download the release candidate and evaluate the necessary
items
includin
Re: [VOTE] Release Apache NiFi 2.0.0-M3 (RC1)
+1 (non-binding) - went through the helper guide, - did a full build with contrib check - verified signatures and hashes Environment: - macOS Version 14.3.1 - OpenJDK Runtime Environment Zulu21.28+85-CA (build 21+35) - Apache Maven 3.9.6 Created and ran some simple flows. Thanks for RMing David! Regards, Mark Krisztina Zsihovszki ezt írta (időpont: 2024. máj. 16., Cs, 10:40): > +1 (non-binding) > > - Verified signatures and hashes > - Ran build using Maven 3.9.5 on macOS 13.5 with Java 21-zulu (build 21+35) > - Contrib check, unit tests passed > > Verified these tickets: > > [NIFI-13146] - ConsumeSlack processor rate limited > [NIFI-12732] - ListS3 should reset its tracking state after configuration > change > > Thanks for RMing, David! > > On Thu, May 16, 2024 at 9:27 AM Ferenc Kis > wrote: > > > +1 (non-binding) > > > > Went through the helper guide, local maven repo cleaned up, full clean > > build with contrib check, verified signatures and hashes > > > > Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae) > > Maven home: /Users/fkis/.sdkman/candidates/maven/current > > Java version: 21.0.3, vendor: Azul Systems, Inc., runtime: > > /Users/fkis/.sdkman/candidates/java/21.0.3-zulu/zulu-21.jdk/Contents/Home > > Default locale: en_HU, platform encoding: UTF-8 > > OS name: "mac os x", version: "14.4.1", arch: "aarch64", family: "mac" > > > > Validations performed: > > - Started NiFi, created a simple flow with ListenHTTP and Input Port. > > Validated ListenHTTP processor is able to receive data > > - Started MiNiFi Java: > > * created a simple GenerateFlowFile -> InvokeHttp flow and > > GenerateFlowFile -> RemoteProcessGroup flow and pushed to MiNiFi via C2 > > protocol > > * Validated that connectivity between NiFi and MiNiFi works via both > > InvokeHTTP and S2S > > - NIFI-13019 ClassNotFoundException when using HandleHttpRequest in > > MiNiFi-2.0.0-M2 > > - NIFI-13123 [MiNiFi] Async C2 Operation Queue > > > > Thanks for RMing David! > > > > Regards > > Ferenc > > > > On Thu, May 16, 2024 at 3:44 AM Csaba Bejan > wrote: > > > > > +1 (binding) > > > > > >- Went through the helper guide and did a clean build > > >- Verified signatures and hashes > > >- Built on OSX 14.2.1 > > >- Java version: Zulu21.28+85-CA (build 21+35) > > >- Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546) > > >- Started NiFi and created a simple flow > > >- Started MiNiFi and verified integration with C2 Server. Played > > around > > >with the C2 protocol (Operations - Update, Transfer, Describe...) > > > > > > Verified: > > > > > >- NIFI-13123 [MiNiFi] Async C2 Operation Queue > > >- NIFI-13019 ClassNotFoundException when using HandleHttpRequest in > > >MiNiFi-2.0.0-M2 > > > > > > Thanks for RMing, David! > > > > > > Regards, > > > Csaba > > > > > > On Mon, May 13, 2024 at 11:49 PM David Handermann < > > > exceptionfact...@apache.org> wrote: > > > > > > > Team, > > > > > > > > I am pleased to be calling this vote for the source release of Apache > > > > NiFi 2.0.0-M3. > > > > > > > > Please review the following guide for how to verify a release > candidate > > > > build: > > > > > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification > > > > > > > > The source being voted on and the convenience binaries are available > > > > on the Apache Distribution Repository: > > > > > > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-2.0.0-M3 > > > > > > > > The build artifacts are available on the Apache Nexus Repository: > > > > > > > > > https://repository.apache.org/content/repositories/orgapachenifi-1269 > > > > > > > > Git Tag: nifi-2.0.0-M3-RC1 > > > > Git Commit ID: f2215c6522a5571189290760c55f0317f8562cbd > > > > GitHub Commit Link: > > > > > > > > > > > > > > https://github.com/apache/nifi/commit/f2215c6522a5571189290760c55f0317f8562cbd > > > > > > > > Checksums of nifi-2.0.0-M3-source-release.zip > > > > > > > > SHA256: > > d471a0a9e4e04faf13bbe13c7d83be6f8002fba598bf0968a3c1b339802a185a >
Re: [VOTE] Release Apache NiFi 2.0.0-M3 (RC1)
+1 (non-binding) - Verified signatures and hashes - Ran build using Maven 3.9.5 on macOS 13.5 with Java 21-zulu (build 21+35) - Contrib check, unit tests passed Verified these tickets: [NIFI-13146] - ConsumeSlack processor rate limited [NIFI-12732] - ListS3 should reset its tracking state after configuration change Thanks for RMing, David! On Thu, May 16, 2024 at 9:27 AM Ferenc Kis wrote: > +1 (non-binding) > > Went through the helper guide, local maven repo cleaned up, full clean > build with contrib check, verified signatures and hashes > > Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae) > Maven home: /Users/fkis/.sdkman/candidates/maven/current > Java version: 21.0.3, vendor: Azul Systems, Inc., runtime: > /Users/fkis/.sdkman/candidates/java/21.0.3-zulu/zulu-21.jdk/Contents/Home > Default locale: en_HU, platform encoding: UTF-8 > OS name: "mac os x", version: "14.4.1", arch: "aarch64", family: "mac" > > Validations performed: > - Started NiFi, created a simple flow with ListenHTTP and Input Port. > Validated ListenHTTP processor is able to receive data > - Started MiNiFi Java: > * created a simple GenerateFlowFile -> InvokeHttp flow and > GenerateFlowFile -> RemoteProcessGroup flow and pushed to MiNiFi via C2 > protocol > * Validated that connectivity between NiFi and MiNiFi works via both > InvokeHTTP and S2S > - NIFI-13019 ClassNotFoundException when using HandleHttpRequest in > MiNiFi-2.0.0-M2 > - NIFI-13123 [MiNiFi] Async C2 Operation Queue > > Thanks for RMing David! > > Regards > Ferenc > > On Thu, May 16, 2024 at 3:44 AM Csaba Bejan wrote: > > > +1 (binding) > > > >- Went through the helper guide and did a clean build > >- Verified signatures and hashes > >- Built on OSX 14.2.1 > >- Java version: Zulu21.28+85-CA (build 21+35) > >- Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546) > >- Started NiFi and created a simple flow > >- Started MiNiFi and verified integration with C2 Server. Played > around > >with the C2 protocol (Operations - Update, Transfer, Describe...) > > > > Verified: > > > >- NIFI-13123 [MiNiFi] Async C2 Operation Queue > >- NIFI-13019 ClassNotFoundException when using HandleHttpRequest in > >MiNiFi-2.0.0-M2 > > > > Thanks for RMing, David! > > > > Regards, > > Csaba > > > > On Mon, May 13, 2024 at 11:49 PM David Handermann < > > exceptionfact...@apache.org> wrote: > > > > > Team, > > > > > > I am pleased to be calling this vote for the source release of Apache > > > NiFi 2.0.0-M3. > > > > > > Please review the following guide for how to verify a release candidate > > > build: > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification > > > > > > The source being voted on and the convenience binaries are available > > > on the Apache Distribution Repository: > > > > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-2.0.0-M3 > > > > > > The build artifacts are available on the Apache Nexus Repository: > > > > > > https://repository.apache.org/content/repositories/orgapachenifi-1269 > > > > > > Git Tag: nifi-2.0.0-M3-RC1 > > > Git Commit ID: f2215c6522a5571189290760c55f0317f8562cbd > > > GitHub Commit Link: > > > > > > > > > https://github.com/apache/nifi/commit/f2215c6522a5571189290760c55f0317f8562cbd > > > > > > Checksums of nifi-2.0.0-M3-source-release.zip > > > > > > SHA256: > d471a0a9e4e04faf13bbe13c7d83be6f8002fba598bf0968a3c1b339802a185a > > > SHA512: > > > > > > cd0b8bbd3fe4ea7ebe8cdac6ac8a7afa97fd7b6a521c2cbcb2c0cdc94899b652bf3726c8fe432e16f44a9dc81907414bbb42e03113f0cd9fb51aa1de9cd727a7 > > > > > > Release artifacts are signed with the following key: > > > > > > https://people.apache.org/keys/committer/exceptionfactory.asc > > > > > > KEYS file is available on the Apache Distribution Repository: > > > > > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > > > Issues resolved for this version: 411 > > > > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354155 > > > > > > Release note highlights can be found on the project wiki: > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0-M3 > > > > > > 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. > > > Then please vote: > > > > > > [] +1 Release this package as nifi-2.0.0-M3 > > > [] +0 no opinion > > > [] -1 Do not release this package because... > > > > > >
Re: [VOTE] Release Apache NiFi 2.0.0-M3 (RC1)
+1 (non-binding) Went through the helper guide, local maven repo cleaned up, full clean build with contrib check, verified signatures and hashes Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae) Maven home: /Users/fkis/.sdkman/candidates/maven/current Java version: 21.0.3, vendor: Azul Systems, Inc., runtime: /Users/fkis/.sdkman/candidates/java/21.0.3-zulu/zulu-21.jdk/Contents/Home Default locale: en_HU, platform encoding: UTF-8 OS name: "mac os x", version: "14.4.1", arch: "aarch64", family: "mac" Validations performed: - Started NiFi, created a simple flow with ListenHTTP and Input Port. Validated ListenHTTP processor is able to receive data - Started MiNiFi Java: * created a simple GenerateFlowFile -> InvokeHttp flow and GenerateFlowFile -> RemoteProcessGroup flow and pushed to MiNiFi via C2 protocol * Validated that connectivity between NiFi and MiNiFi works via both InvokeHTTP and S2S - NIFI-13019 ClassNotFoundException when using HandleHttpRequest in MiNiFi-2.0.0-M2 - NIFI-13123 [MiNiFi] Async C2 Operation Queue Thanks for RMing David! Regards Ferenc On Thu, May 16, 2024 at 3:44 AM Csaba Bejan wrote: > +1 (binding) > >- Went through the helper guide and did a clean build >- Verified signatures and hashes >- Built on OSX 14.2.1 >- Java version: Zulu21.28+85-CA (build 21+35) >- Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546) >- Started NiFi and created a simple flow >- Started MiNiFi and verified integration with C2 Server. Played around >with the C2 protocol (Operations - Update, Transfer, Describe...) > > Verified: > >- NIFI-13123 [MiNiFi] Async C2 Operation Queue >- NIFI-13019 ClassNotFoundException when using HandleHttpRequest in >MiNiFi-2.0.0-M2 > > Thanks for RMing, David! > > Regards, > Csaba > > On Mon, May 13, 2024 at 11:49 PM David Handermann < > exceptionfact...@apache.org> wrote: > > > Team, > > > > I am pleased to be calling this vote for the source release of Apache > > NiFi 2.0.0-M3. > > > > Please review the following guide for how to verify a release candidate > > build: > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification > > > > The source being voted on and the convenience binaries are available > > on the Apache Distribution Repository: > > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-2.0.0-M3 > > > > The build artifacts are available on the Apache Nexus Repository: > > > > https://repository.apache.org/content/repositories/orgapachenifi-1269 > > > > Git Tag: nifi-2.0.0-M3-RC1 > > Git Commit ID: f2215c6522a5571189290760c55f0317f8562cbd > > GitHub Commit Link: > > > > > https://github.com/apache/nifi/commit/f2215c6522a5571189290760c55f0317f8562cbd > > > > Checksums of nifi-2.0.0-M3-source-release.zip > > > > SHA256: d471a0a9e4e04faf13bbe13c7d83be6f8002fba598bf0968a3c1b339802a185a > > SHA512: > > > cd0b8bbd3fe4ea7ebe8cdac6ac8a7afa97fd7b6a521c2cbcb2c0cdc94899b652bf3726c8fe432e16f44a9dc81907414bbb42e03113f0cd9fb51aa1de9cd727a7 > > > > Release artifacts are signed with the following key: > > > > https://people.apache.org/keys/committer/exceptionfactory.asc > > > > KEYS file is available on the Apache Distribution Repository: > > > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > Issues resolved for this version: 411 > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354155 > > > > Release note highlights can be found on the project wiki: > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0-M3 > > > > 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. > > Then please vote: > > > > [] +1 Release this package as nifi-2.0.0-M3 > > [] +0 no opinion > > [] -1 Do not release this package because... > > >
Re: [VOTE] Release Apache NiFi 2.0.0-M3 (RC1)
+1 (binding) - Went through the helper guide and did a clean build - Verified signatures and hashes - Built on OSX 14.2.1 - Java version: Zulu21.28+85-CA (build 21+35) - Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546) - Started NiFi and created a simple flow - Started MiNiFi and verified integration with C2 Server. Played around with the C2 protocol (Operations - Update, Transfer, Describe...) Verified: - NIFI-13123 [MiNiFi] Async C2 Operation Queue - NIFI-13019 ClassNotFoundException when using HandleHttpRequest in MiNiFi-2.0.0-M2 Thanks for RMing, David! Regards, Csaba On Mon, May 13, 2024 at 11:49 PM David Handermann < exceptionfact...@apache.org> wrote: > Team, > > I am pleased to be calling this vote for the source release of Apache > NiFi 2.0.0-M3. > > Please review the following guide for how to verify a release candidate > build: > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification > > The source being voted on and the convenience binaries are available > on the Apache Distribution Repository: > > https://dist.apache.org/repos/dist/dev/nifi/nifi-2.0.0-M3 > > The build artifacts are available on the Apache Nexus Repository: > > https://repository.apache.org/content/repositories/orgapachenifi-1269 > > Git Tag: nifi-2.0.0-M3-RC1 > Git Commit ID: f2215c6522a5571189290760c55f0317f8562cbd > GitHub Commit Link: > > https://github.com/apache/nifi/commit/f2215c6522a5571189290760c55f0317f8562cbd > > Checksums of nifi-2.0.0-M3-source-release.zip > > SHA256: d471a0a9e4e04faf13bbe13c7d83be6f8002fba598bf0968a3c1b339802a185a > SHA512: > cd0b8bbd3fe4ea7ebe8cdac6ac8a7afa97fd7b6a521c2cbcb2c0cdc94899b652bf3726c8fe432e16f44a9dc81907414bbb42e03113f0cd9fb51aa1de9cd727a7 > > Release artifacts are signed with the following key: > > https://people.apache.org/keys/committer/exceptionfactory.asc > > KEYS file is available on the Apache Distribution Repository: > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > Issues resolved for this version: 411 > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354155 > > Release note highlights can be found on the project wiki: > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0-M3 > > 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. > Then please vote: > > [] +1 Release this package as nifi-2.0.0-M3 > [] +0 no opinion > [] -1 Do not release this package because... >
Re: [VOTE] Release Apache NiFi 2.0.0-M3 (RC1)
+1 (non-binding) Verified signature and hashes. Performed full build starting from an empty local maven repo. Maven: 3.9.6 Java 21.0.2, Eclipse Adoptium Ubuntu 24.04.4 Installed binary and started NiFi with all default settings. Ran simple flow and interacted with the UI, looked at metrics, provenance, etc. No issues noted. Note: I had trouble building on CentOS 7 due to some issue with NPM. It may be outdated packages, and since CentOS is end of life, it is not worth down-voting, IMO. On Wed, May 15, 2024 at 6:30 PM Paul Grey wrote: > +1 (non-binding) > > - Verified signatures and hashes of [ > https://dist.apache.org/repos/dist/dev/nifi/nifi-2.0.0-M3/] binaries > - Build of source successful (macOS 14 / Zulu21.28+85-CA (build 21+35)) > - Configuration of three node dev cluster (Manual Keystore Generation) > - Application startup successful (set-single-user-credentials, dev cluster) > - Verified successful flow of data using known good flows (Kafka, > PublishSlack) > - Light testing of load balance operations > - Connection / Round-Robin strategy > - Light testing of cluster disconnect / offload / connect operations > - No FlowFile activity > - Light FlowFile activity > - NIFI-13249 logged for transient offload failure > > > > On Mon, May 13, 2024 at 11:49 PM David Handermann < > exceptionfact...@apache.org> wrote: > > > Team, > > > > I am pleased to be calling this vote for the source release of Apache > > NiFi 2.0.0-M3. > > > > Please review the following guide for how to verify a release candidate > > build: > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification > > > > The source being voted on and the convenience binaries are available > > on the Apache Distribution Repository: > > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-2.0.0-M3 > > > > The build artifacts are available on the Apache Nexus Repository: > > > > https://repository.apache.org/content/repositories/orgapachenifi-1269 > > > > Git Tag: nifi-2.0.0-M3-RC1 > > Git Commit ID: f2215c6522a5571189290760c55f0317f8562cbd > > GitHub Commit Link: > > > > > https://github.com/apache/nifi/commit/f2215c6522a5571189290760c55f0317f8562cbd > > > > Checksums of nifi-2.0.0-M3-source-release.zip > > > > SHA256: d471a0a9e4e04faf13bbe13c7d83be6f8002fba598bf0968a3c1b339802a185a > > SHA512: > > > cd0b8bbd3fe4ea7ebe8cdac6ac8a7afa97fd7b6a521c2cbcb2c0cdc94899b652bf3726c8fe432e16f44a9dc81907414bbb42e03113f0cd9fb51aa1de9cd727a7 > > > > Release artifacts are signed with the following key: > > > > https://people.apache.org/keys/committer/exceptionfactory.asc > > > > KEYS file is available on the Apache Distribution Repository: > > > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > Issues resolved for this version: 411 > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354155 > > > > Release note highlights can be found on the project wiki: > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0-M3 > > > > 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. > > Then please vote: > > > > [] +1 Release this package as nifi-2.0.0-M3 > > [] +0 no opinion > > [] -1 Do not release this package because... > > >
Re: [VOTE] Release Apache NiFi 2.0.0-M3 (RC1)
+1 (non-binding) - Verified signatures and hashes of [ https://dist.apache.org/repos/dist/dev/nifi/nifi-2.0.0-M3/] binaries - Build of source successful (macOS 14 / Zulu21.28+85-CA (build 21+35)) - Configuration of three node dev cluster (Manual Keystore Generation) - Application startup successful (set-single-user-credentials, dev cluster) - Verified successful flow of data using known good flows (Kafka, PublishSlack) - Light testing of load balance operations - Connection / Round-Robin strategy - Light testing of cluster disconnect / offload / connect operations - No FlowFile activity - Light FlowFile activity - NIFI-13249 logged for transient offload failure On Mon, May 13, 2024 at 11:49 PM David Handermann < exceptionfact...@apache.org> wrote: > Team, > > I am pleased to be calling this vote for the source release of Apache > NiFi 2.0.0-M3. > > Please review the following guide for how to verify a release candidate > build: > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification > > The source being voted on and the convenience binaries are available > on the Apache Distribution Repository: > > https://dist.apache.org/repos/dist/dev/nifi/nifi-2.0.0-M3 > > The build artifacts are available on the Apache Nexus Repository: > > https://repository.apache.org/content/repositories/orgapachenifi-1269 > > Git Tag: nifi-2.0.0-M3-RC1 > Git Commit ID: f2215c6522a5571189290760c55f0317f8562cbd > GitHub Commit Link: > > https://github.com/apache/nifi/commit/f2215c6522a5571189290760c55f0317f8562cbd > > Checksums of nifi-2.0.0-M3-source-release.zip > > SHA256: d471a0a9e4e04faf13bbe13c7d83be6f8002fba598bf0968a3c1b339802a185a > SHA512: > cd0b8bbd3fe4ea7ebe8cdac6ac8a7afa97fd7b6a521c2cbcb2c0cdc94899b652bf3726c8fe432e16f44a9dc81907414bbb42e03113f0cd9fb51aa1de9cd727a7 > > Release artifacts are signed with the following key: > > https://people.apache.org/keys/committer/exceptionfactory.asc > > KEYS file is available on the Apache Distribution Repository: > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > Issues resolved for this version: 411 > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354155 > > Release note highlights can be found on the project wiki: > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0-M3 > > 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. > Then please vote: > > [] +1 Release this package as nifi-2.0.0-M3 > [] +0 no opinion > [] -1 Do not release this package because... >
Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.99.0 (RC4)
+1 (non-binding) verified signature and hashes installed the Windows MSI and ran the service on Windows compiled on Fedora 40 and ran ExecuteScript with lua It mostly worked as expected. I found two minor issues: https://issues.apache.org/jira/browse/MINIFICPP-2374, https://issues.apache.org/jira/browse/MINIFICPP-2375, but neither of these is a showstopper, we'll fix them in the next release. Thank you for RMing! Ferenc
Re: [VOTE] Release Apache NiFi 2.0.0-M3 (RC1)
+1 binding - Ran through the release helper. - Verified signatures and hashes. Thanks for RM'ing David. On Mon, May 13, 2024 at 11:49 PM David Handermann < exceptionfact...@apache.org> wrote: > Team, > > I am pleased to be calling this vote for the source release of Apache > NiFi 2.0.0-M3. > > Please review the following guide for how to verify a release candidate > build: > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification > > The source being voted on and the convenience binaries are available > on the Apache Distribution Repository: > > https://dist.apache.org/repos/dist/dev/nifi/nifi-2.0.0-M3 > > The build artifacts are available on the Apache Nexus Repository: > > https://repository.apache.org/content/repositories/orgapachenifi-1269 > > Git Tag: nifi-2.0.0-M3-RC1 > Git Commit ID: f2215c6522a5571189290760c55f0317f8562cbd > GitHub Commit Link: > > https://github.com/apache/nifi/commit/f2215c6522a5571189290760c55f0317f8562cbd > > Checksums of nifi-2.0.0-M3-source-release.zip > > SHA256: d471a0a9e4e04faf13bbe13c7d83be6f8002fba598bf0968a3c1b339802a185a > SHA512: > cd0b8bbd3fe4ea7ebe8cdac6ac8a7afa97fd7b6a521c2cbcb2c0cdc94899b652bf3726c8fe432e16f44a9dc81907414bbb42e03113f0cd9fb51aa1de9cd727a7 > > Release artifacts are signed with the following key: > > https://people.apache.org/keys/committer/exceptionfactory.asc > > KEYS file is available on the Apache Distribution Repository: > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > Issues resolved for this version: 411 > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354155 > > Release note highlights can be found on the project wiki: > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0-M3 > > 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. > Then please vote: > > [] +1 Release this package as nifi-2.0.0-M3 > [] +0 no opinion > [] -1 Do not release this package because... >
Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.99.0 (RC4)
+1 (binding) - followed the release helper guide (checksums, git, readme, etc.) - built on Mac OS X - built on Arch Linux with GCC 14 and Clang 17 with libc++, using CMake directly - built on Fedora Asahi Remix (aarch64 linux) using the new bootstrap. The python bootstrap doesn't handle it yet, but after patching it, build and manual test worked. I found a bug in ConsumeJournald, but I don't consider it release blocker. MINIFICPP-2373 <https://issues.apache.org/jira/browse/MINIFICPP-2373>- built on Ubuntu 22.04 LTS, and tested a workflow receiving data with ListenHTTP - built on Ubuntu 24.04 LTS in docker, following the manual build steps of the release helper guide, and tested with InvokeHTTP Thanks for the release! Marton On 5/15/24 12:43, Martin Zink wrote: +1 (non-binding) -verified signature, hashes and git commit hash -built it from source with default extensions on RockyLinux 9 (aarch64 and x86_64), macOS 14.4.1 (M1) and Windows 10 (x86_64) using the new python based bootstrap -ran through a couple of C2 initiated flows Everything worked as expected, thanks Gabor for RMing great work, Martin On Wed, May 15, 2024 at 11:12 AM Adam Debreceni wrote: +1 (non-binding) Verified hashes, signatures, source, built on macos, pushed a flow on c2, containing a python processor using the nifi api. Everything works as expected. Thank you! On Mon, May 13, 2024 at 10:45 AM Gábor Gyimesi wrote: Hello, I am pleased to be calling this vote for the source release of Apache NiFi MiNiFi C++ 0.99.0. The source tarball, some binary builds, plus signatures and digests can be found at: https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.99.0/ The Git tag is minifi-cpp-0.99.0-RC4 The Git commit ID is 2e9e78cd72cea8c97460bc7db2cb584e5deb3c8f https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=2e9e78cd72cea8c97460bc7db2cb584e5deb3c8f Checksums of nifi-minifi-cpp-0.99.0-source.tar.gz: SHA256: d6982ad6343d42c57c63e7503bb3ba55ddeb1f1cdbbd31064018ec06148b4b3b SHA512: 333f284cd546501612c695ce0dd288ca35fa0bc0ae5a905d4fb54e9494b51fc76e5d4d7de387f07d9ac8be158f022975c5cf487a6e19f12ac6020c4d60f58ab2 Release artifacts are signed with the following key: https://people.apache.org/keys/committer/lordgamez.asc A helpful reminder on how the release candidate verification process works: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173087303 KEYS file available here: https://dist.apache.org/repos/dist/release/nifi/KEYS 124 issues were closed/resolved for this release: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321520=12353618 Release note highlights can be found here: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65145325#ReleaseNotesMiNiFi(C++)-Versioncpp-0.99.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. Then please vote: [ ] +1 Release this package as nifi-minifi-cpp-0.99.0 [ ] +0 no opinion [ ] -1 Do not release this package because...
Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.99.0 (RC4)
+1 (non-binding) -verified signature, hashes and git commit hash -built it from source with default extensions on RockyLinux 9 (aarch64 and x86_64), macOS 14.4.1 (M1) and Windows 10 (x86_64) using the new python based bootstrap -ran through a couple of C2 initiated flows Everything worked as expected, thanks Gabor for RMing great work, Martin On Wed, May 15, 2024 at 11:12 AM Adam Debreceni wrote: > > +1 (non-binding) > > Verified hashes, signatures, source, built on macos, pushed a flow on c2, > containing a python processor using the nifi api. > Everything works as expected. > > Thank you! > > On Mon, May 13, 2024 at 10:45 AM Gábor Gyimesi wrote: > > > Hello, > > > > I am pleased to be calling this vote for the source release of Apache NiFi > > MiNiFi C++ 0.99.0. > > > > The source tarball, some binary builds, plus signatures and digests can be > > found at: > > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.99.0/ > > > > The Git tag is minifi-cpp-0.99.0-RC4 > > The Git commit ID is 2e9e78cd72cea8c97460bc7db2cb584e5deb3c8f > > > > https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=2e9e78cd72cea8c97460bc7db2cb584e5deb3c8f > > > > Checksums of nifi-minifi-cpp-0.99.0-source.tar.gz: > > SHA256: d6982ad6343d42c57c63e7503bb3ba55ddeb1f1cdbbd31064018ec06148b4b3b > > SHA512: > > > > 333f284cd546501612c695ce0dd288ca35fa0bc0ae5a905d4fb54e9494b51fc76e5d4d7de387f07d9ac8be158f022975c5cf487a6e19f12ac6020c4d60f58ab2 > > > > Release artifacts are signed with the following key: > > https://people.apache.org/keys/committer/lordgamez.asc > > > > A helpful reminder on how the release candidate verification process works: > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173087303 > > > > KEYS file available here: > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > 124 issues were closed/resolved for this release: > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321520=12353618 > > > > Release note highlights can be found here: > > > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65145325#ReleaseNotesMiNiFi(C++)-Versioncpp-0.99.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. Then please vote: > > > > [ ] +1 Release this package as nifi-minifi-cpp-0.99.0 > > [ ] +0 no opinion > > [ ] -1 Do not release this package because... > >
Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.99.0 (RC4)
+1 (non-binding) Verified hashes, signatures, source, built on macos, pushed a flow on c2, containing a python processor using the nifi api. Everything works as expected. Thank you! On Mon, May 13, 2024 at 10:45 AM Gábor Gyimesi wrote: > Hello, > > I am pleased to be calling this vote for the source release of Apache NiFi > MiNiFi C++ 0.99.0. > > The source tarball, some binary builds, plus signatures and digests can be > found at: > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.99.0/ > > The Git tag is minifi-cpp-0.99.0-RC4 > The Git commit ID is 2e9e78cd72cea8c97460bc7db2cb584e5deb3c8f > > https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=2e9e78cd72cea8c97460bc7db2cb584e5deb3c8f > > Checksums of nifi-minifi-cpp-0.99.0-source.tar.gz: > SHA256: d6982ad6343d42c57c63e7503bb3ba55ddeb1f1cdbbd31064018ec06148b4b3b > SHA512: > > 333f284cd546501612c695ce0dd288ca35fa0bc0ae5a905d4fb54e9494b51fc76e5d4d7de387f07d9ac8be158f022975c5cf487a6e19f12ac6020c4d60f58ab2 > > Release artifacts are signed with the following key: > https://people.apache.org/keys/committer/lordgamez.asc > > A helpful reminder on how the release candidate verification process works: > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173087303 > > KEYS file available here: > https://dist.apache.org/repos/dist/release/nifi/KEYS > > 124 issues were closed/resolved for this release: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321520=12353618 > > Release note highlights can be found here: > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65145325#ReleaseNotesMiNiFi(C++)-Versioncpp-0.99.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. Then please vote: > > [ ] +1 Release this package as nifi-minifi-cpp-0.99.0 > [ ] +0 no opinion > [ ] -1 Do not release this package because... >
Inquiry Regarding Missing Documentation for selectHive3QL in nifi-hive3-nar for NiFi 1.25.0
Dear NiFi Development Team, I hope this message finds you well. I am currently working with Apache NiFi 1.25.0 and it's already operational in our data processing pipeline. In my research, I've noticed a scarcity of documentation regarding the selectHive3QL processor, specifically on the official NiFi documentation website. I'd greatly appreciate any information you could provide on why the selectHive3QL processor's documentation is not available on the NiFi website, or if there are plans to include it in the future. I believe comprehensive documentation for each processor in NiFi is essential for users to maximise the potential of this powerful platform. I look forward to your response. Thank you in advance. Best Regard, Jing
