Re: [VOTE] Release Apache NiFi 2.0.0-M3 (RC1)

[Robert Fellows]

+1 non-binding

Verified hashes/signature.
Verified full build with tests.
Tested the new UI.
  * Built a simple flow
  * Added a Github Registry Client
  * Imported a more complicated flow from the github registry client
  * Both Dark and Light mode look great!

Thanks for RM'ing, David!

-- Rob Fellows

On Tue, May 14, 2024 at 4:22 AM Joe Witt  wrote:

> +1 binding.
>
> Verified full clean build with contrib check and all unit tests pass.
> Ran entire integration/system test suite including python components.  All
> pass.
> Built and deployed maven docker image.  All good.
> Ran a flow which leverages both Java and Python based extensions.  All
> good.
> Ran dependency update reports.  Looks good but did file [1]
> Ran dependency-check vuln reporting and do note a series of findings which
> look new and need review/follow-up.
>
> [1] https://issues.apache.org/jira/browse/NIFI-13227
>
> Thanks David for RM.
>
> Thanks everyone.  We've had 30 different contributors in the past month and
> have a new surge in commits higher than we've seen since 2016!
>
> On Tue, May 14, 2024 at 4:48 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-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...
> >
>


-- 
---
Rob Fellows

Re: [DISCUSS] UI Contributions

[Robert Fellows]

The new UI has progressed quite well and I agree with this stance. However,
with 2.0 getting close, one could argue that new UI features should
definitely land in the new UI but only really need to land in the original
UI if desired or to support backward compatibility.

--Rob

On Tue, Apr 23, 2024 at 7:55 PM Scott Aslan  wrote:

> Thanks for sending this out Matt! I agree that at this point any new
> features to the frontend should be implemented in both the new and the
> existing UI. Updating the contributions guidelines seems appropriate as
> well.
>
> -Scott
>
> On Tue, Apr 23, 2024 at 4:07 PM Matt Gilman  wrote:
>
> > Team,
> >
> > Substantial progress has been made on modernizing the NiFi UI under [1]
> and
> > [2]. As detailed in the JIRAs, this effort has been largely motivated by
> > moving away from deprecated and unsupported dependencies. As we begin the
> > process to transition to the new UI, we are at a point where any UI
> > contributions should target both the new UI and the existing UI. We've
> > updated the PR template detailing this and the README for the new UI [3]
> to
> > help introduce folks making UI contributions to the layout of the
> > repository. It discusses the steps needed to build NiFi with the new UI
> > included and how to access it.
> >
> > Happy to discuss any questions folks may have.
> >
> > Matt
> >
> > [1] https://issues.apache.org/jira/browse/NIFI-11481
> > [2] https://issues.apache.org/jira/browse/NIFI-12400
> > [3] https://github.com/apache/nifi/pull/8693
> >
>


-- 
---
Rob Fellows

Re: [VOTE] Release Apache NiFi 2.0.0-M2 (RC4)

[Robert Fellows]

+1 non-binding

verified hashes
build with java 21
ran simple flow
built with new UI


On Fri, Jan 26, 2024 at 12:11 PM Nissim Shiman 
wrote:

>  +1 (non-binding)
>
> verified source release sha256/512 checksums
>
> successfully ran build using:
> Apache Maven 3.9.6
> Java 21 2023-09-19 LTS
> linux kernel 3.10.0-1160
>
> Ran various simple flows successfully.  Migrated registry from 1.24 and
> 2.0.0-M1 to this RC successfully.  (i.e. and tested importing PGs,
> committing new versions of PGs to registry successfully, both from nifi and
> filesystem).  Verified flows were persisted in registry after registry
> restart as well.
>
> Noticed non-blocking issue where reporting tasks' link to referenced
> controller service is not completely working.  Created NIFI-12678 for it.
>
> Tested:
> NIFI-11389 Controller Services's link to referencing Controller Services
> components not always working
> NIFI-12387 Flow Configuration History can record a Comments change for
> Controller Service when no changes have been made
>
> NIFI-12394 when importing versioned flow with component that migrates
> properties, controller service reference is invalid
> NIFI-12666 Correct NiFi Registry Data Source Configuration
>
> Thank you David and team for the upcoming release!
>
> Nissim Shiman
>
> On Friday, January 26, 2024 at 02:30:45 AM UTC, 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-M2.
>
> 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-M2
>
> The build artifacts are available on the Apache Nexus Repository:
>
> https://repository.apache.org/content/repositories/orgapachenifi-1264
>
> Git Tag: nifi-2.0.0-M2-RC4
> Git Commit ID: 640b7bdfbbb8842f057a9bf49dc2b9b5d092abda
> GitHub Commit Link:
>
> https://github.com/apache/nifi/commit/640b7bdfbbb8842f057a9bf49dc2b9b5d092abda
>
> Checksums of nifi-2.0.0-M2-source-release.zip
>
> SHA256: 1946eceb3ae4f541545e93ddc6dd2cbe2a3302a6a46e6c584f3ffc1c1bd1e18b
> SHA512:
> e8e67e1e67359553479c0721a1c49ae6706cc6882eadf92e1f5ccc2619637ab87119a06221980d4c34d99b7b6d9a2138c77440b407074090e727b5d4447ab799
>
> 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: 214
>
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12353861
>
> Release note highlights can be found on the project wiki:
>
>
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0-M2
>
> 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-M2
> [] +0 no opinion
> [] -1 Do not release this package because...
>



-- 
---
Rob Fellows

Re: [VOTE] Release Apache NiFi 2.0.0-M2 (RC3)

[Robert Fellows]

+1 non-binding

*verified hashes*

*built with:*
openjdk version "21.0.1" 2023-10-17 LTS
OpenJDK Runtime Environment Zulu21.30+15-CA (build 21.0.1+12-LTS)
OpenJDK 64-Bit Server VM Zulu21.30+15-CA (build 21.0.1+12-LTS, mixed mode,
sharing)

General usage of the application looks good. Added a couple of the new
processors and services without issue.


On Thu, Jan 25, 2024 at 8:11 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-M2.
>
> 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-M2
>
> The build artifacts are available on the Apache Nexus Repository:
>
> https://repository.apache.org/content/repositories/orgapachenifi-1262
>
> Git Tag: nifi-2.0.0-M2-RC3
> Git Commit ID: 439ac5f596fe90d2591376caec1499ed86abfd6b
> GitHub Commit Link:
>
> https://github.com/apache/nifi/commit/439ac5f596fe90d2591376caec1499ed86abfd6b
>
> Checksums of nifi-2.0.0-M2-source-release.zip
>
> SHA256: 0637647ba7b6b8f0743cf00d95dd3e99250f2737ae9583daee511477cad22847
> SHA512:
> 56d6c196ec64884c56a65278f7dd32cc62f1595ff5b2ec37403dcd54b7757a9ac70aa75a50ee6f61237e37b486d32b1ebbf95a4e38a2ea5dc7f694c779d5c6c4
>
> 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: 207
>
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12353861
>
> Release note highlights can be found on the project wiki:
>
>
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0-M2
>
> 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-M2
> [] +0 no opinion
> [] -1 Do not release this package because...
>


-- 
---
Rob Fellows

Re: [VOTE] Release Apache NiFi 1.23.0 (RC3)

[Robert Fellows]

+1 (non-binding)

Verified sig, hashes.
Built with JDK 11.0.16 (zulu).
Ran simple flow scenarios.

On Tue, Jul 25, 2023 at 5:32 PM David Handermann <
exceptionfact...@apache.org> wrote:

> Team,
>
> I am pleased to be calling this vote for the source release of Apache NiFi
> 1.23.0.
>
> Please review the following guide for how to verify a release candidate
> build:
>
>
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
>
> The source being voted upon and the convenience binaries are available on
> the Apache Distribution Repository:
>
> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.23.0/
>
> The build artifacts are available on the Apache Nexus Repository:
>
> https://repository.apache.org/content/repositories/orgapachenifi-1233
>
> Git Tag: nifi-1.23.0-RC3
> Git Commit ID: 27a690a30a6ae77c217a47ac0601e85970777ca2
> GitHub Commit Link:
>
> https://github.com/apache/nifi/commit/27a690a30a6ae77c217a47ac0601e85970777ca2
>
> Checksums of nifi-1.23.0-source-release.zip:
>
> SHA256: 39c97d89804b005cc995c56a87a3df6f68c44ee42114dffe756bbac90a3593cf
> SHA512:
>
> f256ca731a67435e9883626931abc58f28cda9deb6a7d0a84ed97b78104e43b3b638ee2297d79f92bf5a1e19f62cc78e0a886fa0094593ab34b21d658c59eadd
>
> Release artifacts are signed with the following key:
>
> https://people.apache.org/keys/committer/exceptionfactory.asc
>
> KEYS file available here:
>
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 132 issues were closed/resolved for this release:
>
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12353320
>
> Release note highlights can be found here:
>
>
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.23.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.23.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>


-- 
---
Rob Fellows

Re: [VOTE] Adopt NiFi 2.0 Proposed Release Goals

[Robert Fellows]

+1 (non-binding)

On Tue, Dec 13, 2022 at 11:10 AM Mike Thomsen 
wrote:

> +1 binding
>
> On Tue, Dec 13, 2022 at 9:33 AM Mark Bean  wrote:
> >
> > +1 (non-binding)
> >
> > On Mon, Dec 12, 2022 at 12:02 PM David Handermann <
> > exceptionfact...@apache.org> wrote:
> >
> > > Team,
> > >
> > > Following positive feedback on NiFi 2.0 Proposed Release Goals [1] on
> the
> > > recent discussion thread [2], I am calling this vote to adopt the
> following
> > > as Release Goals for NiFi 2.0:
> > >
> > > 1. Remove Java 8 support and require Java 11
> > > 2. Remove deprecated components
> > > 3. Remove deprecated component properties
> > > 4. Remove components integrating with unmaintained services
> > > 5. Remove compatibility classes and methods
> > > 6. Remove flow.xml.gz in favor of flow.json.gz
> > > 7. Remove duplicative features
> > > 8. Upgrade internal Java API references
> > > 9. Reorganize standard components
> > > 10. Implement migration tools for upgrading flows
> > >
> > > A positive vote indicates agreement on these goals and the initiation
> of
> > > the following actions:
> > >
> > > 1. Rename NiFi 2.0 Proposed Release Goals to NiFi 2.0 Release Goals
> > > 2. Create version 1 branch in Git for subsequent support releases on
> the
> > > version 1 series
> > > 3. Update the current main branch in Git to version 2.0.0-SNAPSHOT
> > >
> > > The vote will be open for 72 hours and follow standard procedures for
> > > release votes.
> > >
> > > Please review the linked goals and discussions for background.
> > >
> > > [ ] +1 Adopt NiFi 2.0 Release Goals
> > > [ ] +0 No opinion
> > > [ ] -1 Do not adopt NiFi 2.0 Release Goals for the following reasons...
> > >
> > > [1]
> > >
> > >
> https://cwiki.apache.org/confluence/display/NIFI/NiFi+2.0+Proposed+Release+Goals
> > > [2] https://lists.apache.org/thread/xo77p9t3xg4k70356xrqbdg4m9sg7sf8
> > >
>


-- 
---
Rob Fellows

Re: [VOTE] Release Apache NiFi 1.17.0 (RC2)

[Robert Fellows]

+1 (non-binding)

Ran through the release helper guide. DId some smoke testing. Looks good to
me.

Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Java version: 1.8.0_292, vendor: AdoptOpenJDK
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac"



On Thu, Jul 28, 2022 at 4:54 PM Andrew Lim 
wrote:

> +1 (binding)
>
> -Ran full clean install on OS X (Catalina 10.15.7, OpenJDK version
> 1.8.0_252)
> -Tested secure NiFi with secure NiFi Registry
> -Ran basic flows successfully; tested basic versioned flow functionality
> -Reviewed/tested Core UI fixes and documentation updates
>
> Drew
>
> > On Jul 28, 2022, at 10:28 AM, Joe Witt  wrote:
> >
> > Hello,
> >
> > I am pleased to be calling this vote for the source release of Apache
> NiFi
> > 1.17.0.
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > https://repository.apache.org/content/repositories/orgapachenifi-1210
> >
> > The source being voted upon and the convenience binaries can be found at:
> > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.17.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+release+candidate
> >
> > The Git tag is nifi-1.17.0-RC2
> > The Git commit ID is 8d256784d84cc28bf5642e1bf38dec3eba0c5f23
> >
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=8d256784d84cc28bf5642e1bf38dec3eba0c5f23
> >
> > Checksums of nifi-1.17.0-source-release.zip:
> > SHA256: 8b9b2088ad966329248cfae7792f576f4f30fea4b4e50f055f84724dba4fe8a3
> > SHA512:
> >
> 2429348ad514ca7ab9df86aaa57207f1434044c6f7e947d0950ca9826b4f1aa51061617a17444c086eed19b1f26a5ebbe3b455cafed9d219727adf26ecb5f8d2
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/joewitt.asc
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/release/nifi/KEYS
> >
> > 310 issues were closed/resolved for this release:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12351438
> >
> > Release note highlights can be found here:
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.17.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.17.0
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
>
>

-- 
---
Rob Fellows

Re: [VOTE] Release Apache NiFi 1.16.0 (rc3)

[Robert Fellows]

+1 (non-binding)

Verified signature
Verified hashes
Build on MacOS Big Sur (11.6), JDK 11.0.8.hs-adpt
Walked through a few simple use cases, all looks good.

-- Rob

On Thu, Mar 24, 2022 at 7:09 AM Tony Kurc  wrote:

> +1 (binding)
>
> Verified hashes and signatures. Reviewed notice and license and readme and
> did not see any issues. Build went without issue and ran a simple flow.
>
> Tony
>
>
> On Mon, Mar 21, 2022, 5:42 PM Joe Witt  wrote:
>
> > Hello,
> >
> > I am pleased to be calling this vote for the source release of Apache
> NiFi
> > 1.16.0.
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > https://repository.apache.org/content/repositories/orgapachenifi-1198
> >
> > The source being voted upon and the convenience binaries can be found at:
> > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.16.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+release+candidate
> >
> > The Git tag is nifi-1.16.0-RC3
> > The Git commit ID is b019a9191f1c83bc7f547dc02c1b679b8936acee
> >
> >
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=b019a9191f1c83bc7f547dc02c1b679b8936acee
> >
> > Checksums of nifi-1.16.0-source-release.zip:
> > SHA256: 2f16cb94df404d1bcc9c32835ba98da8940005a5d7ea5504c155ee42021a221e
> > SHA512:
> >
> >
> cbd95f15cec5ffe506fef204526267b18b77d7266f6dc3e1bbc3c7600aac12e119977f7d8cf93dbbbc86fbb0739ba88aaa11a5381d29a463ec9a0c9a18f4e9e6
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/joewitt.asc
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/release/nifi/KEYS
> >
> > 401 issues were closed/resolved for this release:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12350741
> >
> > Release note highlights can be found here:
> >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.16.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.16.0
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
> >
>


-- 
---
Rob Fellows

Re: [ANNOUNCE] New Apache NiFi Committer Paul Grey

[Robert Fellows]

Congrats Paul!

On Wed, Mar 16, 2022 at 9:35 PM Joe Gresock  wrote:

> Congrats, Paul!
>
> On Wed, Mar 16, 2022 at 9:13 PM Kevin Doran 
> wrote:
>
> > Congrats Paul! We’ll deserved
> > 
> > From: Nathan Gough 
> > Sent: Wednesday, March 16, 2022 9:12:21 PM
> > To: dev@nifi.apache.org 
> > Subject: Re: [ANNOUNCE] New Apache NiFi Committer Paul Grey
> >
> > Congrats, Paul! Thanks for your contributions so far.
> >
> > On Wed, Mar 16, 2022 at 9:06 PM Marton Szasz  wrote:
> >
> > > Congratulations, Paul!
> > >
> > > On Thu, 17 Mar 2022 at 00:00, Joe Witt  wrote:
> > > >
> > > > Congrats and thanks!
> > > >
> > > > On Wed, Mar 16, 2022 at 4:55 PM gre...@yahoo.com.INVALID
> > > >  wrote:
> > > >
> > > > > Thanks much!  Next step is to do something about this "yahoo.com"
> > > email
> > > > > address...
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On Wednesday, March 16, 2022, 06:46:02 PM EDT, David Handermann <
> > > > > exceptionfact...@apache.org> wrote:
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Apache NiFi community,
> > > > >
> > > > > On behalf of the Apache NiFi PMC, I am very pleased to announce
> that
> > > Paul
> > > > > Grey
> > > > > has accepted the PMC's invitation to become a committer on the
> Apache
> > > NiFi
> > > > > project.
> > > > >
> > > > > Paul has contributed a number of pull requests and code reviews
> over
> > > the
> > > > > past year, improving project security and test stability in a
> number
> > of
> > > > > areas. We appreciate Paul's work and look forward to continued
> > > > > contributions!
> > > > >
> > > > > Welcome Paul, and congratulations!
> > > > >
> > >
> >
>
-- 
---
Rob Fellows

Re: nifi-registry

[Robert Fellows]

Hello Kostas,
  It looks like you may have forgotten to attach the screenshot that you
referenced. Also, any details/errors that you may see in the javascript
console might be helpful here.

On Fri, Feb 11, 2022 at 7:30 AM kostas patounis  wrote:

> Hello
>
> I am currently trying to run nifi-registry on windows. Everything seems to
> work except I cannot enter the UI. I have JDK 1.8.0_202 on my machine. When
> I execute the nifi-registry.bat file in the terminal I see the picture
> below. Any suggestions?
>
>

-- 
---
Rob Fellows

Re: [VOTE] Release Apache NiFi Flow Design System 0.3.0 RC2

[Robert Fellows]

+1 (non-binding)

Verified signature
Verified hashes
Checked LICENSE and NOTICE
Built with node 16.13.2
Ran demo app, verified a handful of the resolved issues. Everything looks
great!

Thanks for RM'ing Scott!

---
Rob Fellows

Re: [VOTE] Release Apache NiFi Flow Design System 0.3.0

[Robert Fellows]

+1 (non-binding)

With the corrected download links I was able to download, verify signatures
and hashes, build, and exercise FDS components.

* Built with node 16.13.2 / npm 8.1.2

Thanks for RM'ing Scott!

On Mon, Jan 24, 2022 at 7:23 PM Scott Aslan  wrote:

> Hello Apache NiFi community,
>
>
> Please find the associated guidance to help those interested in
> validating/verifying the release so they can vote.
>
>
> # Download latest KEYS file:
>
> https://dist.apache.org/repos/dist/dev/nifi/KEYS
>
>
> # Import keys file:
>
> gpg --import KEYS
>
>
> # Pull down nifi-fds-0.3.0 source release artifacts for review:
>
> wget
>
> https://dist.apache.org/repos/dist/dev/nifi-fds/nifi-fds-0.3.0/nifi-fds-0.3.0-source-release.zip
>
> wget
>
> https://dist.apache.org/repos/dist/dev/nifi-fds/nifi-fds-0.3.0/nifi-fds-0.3.0-source-release.zip.asc
>
> wget
>
> https://dist.apache.org/repos/dist/dev/nifi-fds/nifi-fds-0.3.0/nifi-fds-0.3.0-source-release.zip.sha1
>
> wget
>
> https://dist.apache.org/repos/dist/dev/nifi-fds/nifi-fds-0.3.0/nifi-fds-0.3.0-source-release.zip.sha256
>
> wget
>
> https://dist.apache.org/repos/dist/dev/nifi-fds/nifi-fds-0.3.0/nifi-fds-0.3.0-source-release.zip.sha512
>
>
> # Verify the signature
>
> gpg --verify nifi-fds-0.3.0-source-release.zip.asc
>
>
> # Verify the hashes (sha1, sha256, sha512) match the source and what was
> provided in the vote email thread
>
> sha1sum nifi-fds-0.3.0-source-release.zip
>
> sha256sum nifi-fds-0.3.0-source-release.zip
>
> sha512sum nifi-fds-0.3.0-source-release.zip
>
>
> # Unzip nifi-fds-0.3.0-source-release.zip
>
>
> # Verify the build works and tests pass (npm version >= 8.1.2)
>
> cd nifi-fds-0.3.0
>
> npm run ci
>
> npm run clean:install
>
>
> # Verify the contents contain a good README, NOTICE, and LICENSE.
>
>
> # Verify the git commit ID is correct
>
>
> # Verify the RC was branched off the correct git commit ID
>
>
> # Run the demo-app and verify UI/UX components work as expected
>
> npm run watch
>
>
> NOTE: There will be some warnings displayed in the terminal in the browser.
> These are the webpack dev server telling us that some of our dependencies
> are not providing licenses. This is expected. Simply close the warning
> overlay and you should be able to verify the UX/UI components included in
> the demo application.
>
>
> # Make sure the README, NOTICE, and LICENSE are present and correct
>
>
> # Send a response to the vote thread indicating a +1, 0, -1 based on your
> findings.
>
>
> Thank you for your time and effort to validate the release!
>


-- 
---
Rob Fellows

Re: [VOTE] Release Apache NiFi Flow Design System 0.3.0

[Robert Fellows]

The links for the downloads are incorrect. It should read:

# Pull down nifi-fds-0.3.0 source release artifacts for review:

wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.3.0/nifi-fds-0.3.0-source-release.zip

wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.3.0/nifi-fds-0.3.0-source-release.zip.asc

wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.3.0/nifi-fds-0.3.0-source-release.zip.sha1

wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.3.0/nifi-fds-0.3.0-source-release.zip.sha256

wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.3.0/nifi-fds-0.3.0-source-release.zip.sha512


On Mon, Jan 24, 2022 at 7:23 PM Scott Aslan  wrote:

> Hello Apache NiFi community,
>
>
> Please find the associated guidance to help those interested in
> validating/verifying the release so they can vote.
>
>
> # Download latest KEYS file:
>
> https://dist.apache.org/repos/dist/dev/nifi/KEYS
>
>
> # Import keys file:
>
> gpg --import KEYS
>
>
> # Pull down nifi-fds-0.3.0 source release artifacts for review:
>
> wget
>
> https://dist.apache.org/repos/dist/dev/nifi-fds/nifi-fds-0.3.0/nifi-fds-0.3.0-source-release.zip
>
> wget
>
> https://dist.apache.org/repos/dist/dev/nifi-fds/nifi-fds-0.3.0/nifi-fds-0.3.0-source-release.zip.asc
>
> wget
>
> https://dist.apache.org/repos/dist/dev/nifi-fds/nifi-fds-0.3.0/nifi-fds-0.3.0-source-release.zip.sha1
>
> wget
>
> https://dist.apache.org/repos/dist/dev/nifi-fds/nifi-fds-0.3.0/nifi-fds-0.3.0-source-release.zip.sha256
>
> wget
>
> https://dist.apache.org/repos/dist/dev/nifi-fds/nifi-fds-0.3.0/nifi-fds-0.3.0-source-release.zip.sha512
>
>
> # Verify the signature
>
> gpg --verify nifi-fds-0.3.0-source-release.zip.asc
>
>
> # Verify the hashes (sha1, sha256, sha512) match the source and what was
> provided in the vote email thread
>
> sha1sum nifi-fds-0.3.0-source-release.zip
>
> sha256sum nifi-fds-0.3.0-source-release.zip
>
> sha512sum nifi-fds-0.3.0-source-release.zip
>
>
> # Unzip nifi-fds-0.3.0-source-release.zip
>
>
> # Verify the build works and tests pass (npm version >= 8.1.2)
>
> cd nifi-fds-0.3.0
>
> npm run ci
>
> npm run clean:install
>
>
> # Verify the contents contain a good README, NOTICE, and LICENSE.
>
>
> # Verify the git commit ID is correct
>
>
> # Verify the RC was branched off the correct git commit ID
>
>
> # Run the demo-app and verify UI/UX components work as expected
>
> npm run watch
>
>
> NOTE: There will be some warnings displayed in the terminal in the browser.
> These are the webpack dev server telling us that some of our dependencies
> are not providing licenses. This is expected. Simply close the warning
> overlay and you should be able to verify the UX/UI components included in
> the demo application.
>
>
> # Make sure the README, NOTICE, and LICENSE are present and correct
>
>
> # Send a response to the vote thread indicating a +1, 0, -1 based on your
> findings.
>
>
> Thank you for your time and effort to validate the release!
>


-- 
---
Rob Fellows

Re: [DISCUSS] NiFi Registry -> NiFi consensus

[Robert Fellows]

+1 (non-binding)

On Fri, Jul 16, 2021 at 4:44 PM Otto Fowler  wrote:

>  +1 (non-binding)
>
> From: Matt Burgess  
> Reply: dev@nifi.apache.org  
> Date: July 16, 2021 at 14:20:20
> To: dev@nifi.apache.org  
> Subject:  [DISCUSS] NiFi Registry -> NiFi consensus
>
> All,
>
> We've been asked to record our consensus for the move of NiFi Registry
> to the NiFi codebase in a mailing list thread for posterity. Most
> discussion happened on the PR but INFRA would like a link to this
> thread showing consensus from PMC members, committers, and the
> community.
>
> I didn't put my +1 on the PR but I am in favor of moving the NiFi
> Registry codebase into NiFi :) Please feel free to share your thoughts
> as well.
>
> Thank you,
> Matt
>


-- 
---
Rob Fellows

Re: nifi 1.14.0

[Robert Fellows]

yes,

bin/nifi.sh set-single-user-credentials  

On Fri, Jul 16, 2021 at 6:18 AM Chris Lim 
wrote:

> Is there a way to change the username and password?
>
> Thanks,
> Chris
>
> On Fri, Jul 16, 2021 at 13:35 Chris Sampson
>  wrote:
>
> > The username and password are printed to the logs during startup, you can
> > obtain them there.
> >
> >
> > Cheers,
> >
> > Chris Sampson
> >
> > On Fri, 16 Jul 2021, 06:03 Roberto Vega,  >
> > wrote:
> >
> > > hello team, good morning
> > >
> > > perform the installation of the new update of nifi 1.14.0 on a virtual
> > > machine redhat 8 and I realize that now nifi the security functions are
> > > enabled by default.
> > >
> > > The question is, what is the username and password configured by
> default
> > or
> > > how can I get the credentials
> > >
> > > thanks for the support
> > >
> >
> --
> Sent from my iPhone
>


-- 
---
Rob Fellows

Re: [VOTE] Release Apache NiFi 1.14.0 (rc2)

[Robert Fellows]

+1 (non-binding)

Verified signature and hashes
Full build with contrib check with OpenJDK Runtime Environment AdoptOpenJDK
(build 11.0.8+10)
Started new instance, verified it was secured by default.
Changed the username and password using bin/nifi.sh
set-single-user-credentials
Logged in with the new user/password i created
Fired up registry, created a bucket
Connected nifi to registry, versioned a flow. Imported a flow into another
process group.
General App usage (Firefox 89.0.2)

Thanks for RM'ing this Joe!

-- Rob Fellows

On Sat, Jul 10, 2021 at 9:31 PM Mark Payne  wrote:

> +1 (binding)
>
> Verified the hashes.
> Performed full build with contrib-check profile
> Ran all system tests
> Started the newly created instance, verified that it was secure by default.
> Changed username & password and verified the behavior.
> Created a 2-node cluster, secured by mutual TLS and verified behavior.
>
> Started nifi registry. Created a bucket.
> Pushed to the bucket from standalone instance. Then added a second version
> of flow.
> Downloaded flow onto cluster and switched between versioned a few times.
>
> Verified behavior of new default backpressure thresholds.
> Built a DataFlow and saved to file, then ran it via Stateless NiFi using
> command-line parameter overrides.
> Started DataFlow using Stateless nifi and the kafka connector. Verified
> this behavior.
>
> Encountered no issues this time.
>
> Thanks for putting the RC together, Joe!
>
> > On Jul 10, 2021, at 6:40 PM, Joe Witt  wrote:
> >
> > Hello,
> >
> > I am pleased to be calling this vote for the source release of Apache
> > NiFi 1.14.0.
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > https://repository.apache.org/content/repositories/orgapachenifi-1183
> >
> > The source being voted upon and the convenience binaries can be found at:
> > https://dist.apache.org/repos/dist/dev/nifi/1.14.0/
> >
> > Please note that this release now includes the convenience binaries for
> > Apache NiFi, NiFi toolkit, MiNiFi, MiNiFi Toolkit, Registry, Registry
> Toolkit,
> > and Stateless NiFi.
> >
> > 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+release+candidate
> >
> > The Git tag is nifi-1.14.0-RC2
> > The Git commit ID is fcbf1d5f975dd984e34f3a543b9480c779b0dc2f
> >
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=fcbf1d5f975dd984e34f3a543b9480c779b0dc2f
> >
> > Checksums of nifi-1.14.0-source-release.zip:
> > SHA256: a96cf75c4f82d01e1c8e0b678d5ff23dec8c26824611c8d37f2ec245e9932b1c
> > SHA512:
> 2d23b1a2fae9f545f665c4ee5d9723cdf9c68a62a26d80287b96a55773594e1e80f689ec0f00ba74af92df164c6f4df73ac9b91db7678aaefd69ee8f1eed3f42
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/joewitt.asc
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/release/nifi/KEYS
> >
> > 330+ issues were closed/resolved for this release:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12349644
> >
> > Release note highlights can be found here:
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.14.0
> >
> > The vote will be open for at least 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.14.0
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
>
>

-- 
---
Rob Fellows

Re: [VOTE] Release Apache NiFi 1.13.0 (rc2)

[Robert Fellows]

+1 (non-binding)
Followed the release helper
Tested basic functionality
Apache Maven 3.6.3
Java version: 11.0.8, vendor: AdoptOpenJDK
OS name: "mac os x", version: "10.15.7", arch: "x86_64", family: "mac"

Thanks for RM'ing, Joe.

-- Rob

On Tue, Feb 2, 2021 at 9:46 PM M Tien  wrote:

> +1 (non-binding)
>
> Went through the release helper
> Verified a successful build on
> Zulu OpenJDK 1.8.0_282
> Zulu OpenJDK 11.0.10
> Maven 3.6.2
> OS name: "mac os x", version: "10.15.4", arch: "x86_64", family: "mac"
> Ran a secure instance with OIDC using Google and Okta
> Verified a successful user logout and the JWT is invalidated (NIFI-7584)
> Tested with a flow using the CompressContent processor and verified
> dependent properties (NIFI-1121)
>
> Thanks,
> Margot
>
> > On Feb 2, 2021, at 6:23 PM, Chad Zobrisky  wrote:
> >
> > +1 (non-binding)
> >
> > Verified signatures, checksums, README, NOTICE and LICENSE
> >
> > Built with maven 3.6.3
> > Ubuntu 20.04.1
> > openjdk 11.0.9.1 and openjdk 1.8.0_275
> > Ran on a secure cluster with java 11.0.9.1 - all previous flows ran as
> > expected.
> >
> > Thanks,
> > Chad
> >
> >
> > On Tue, Feb 2, 2021 at 8:15 PM Mark Bean  wrote:
> >
> >> +1 (non-binding)
> >>
> >> Verified signature and checksums
> >> Downloaded source and built with Java 8 and Java 11
> >>  mvn -T 1C clean install -Pcontrib-check,include-grpc
> >>  MacOS, 10.15.7
> >>  Java 11.0.9, x86_64
> >>  Java 1.8.0_282, x86_64
> >>  Maven 3.6.3
> >> Verified README, NOTICE and LICENSE (noting 2020 date in License)
> >> Ran in both Java 8 and Java 11 JVM with a _very_ basic flow. All basic
> >> functions and UI interaction appear normal.
> >>
> >>
> >>
> >> On Tue, Feb 2, 2021 at 7:41 PM Muazma Zahid  wrote:
> >>
> >>>  +1 (non-binding)
> >>>
> >>> - Ran build with OpenJDK 1.8.0_275 on Linux
> >>> - Deployed cluster on Azure and tested standard flows with Blob, ADLS,
> >> and
> >>> CosmosDB processors.
> >>>
> >>> Looks good to me.
> >>>
> >>> Thanks
> >>> Muazma
> >>>
> >>> On Tue, Feb 2, 2021 at 4:35 PM Nathan Gough 
> wrote:
> >>>
>  +1 (non-binding)
> 
>  - Verified signature and checksums again
>  - Ran build with
>  java -version
> 
>  openjdk version "1.8.0_282"
> 
>  OpenJDK Runtime Environment (Zulu 8.52.0.23-CA-macosx) (build
>  1.8.0_282-b08)
> 
>  OpenJDK 64-Bit Server VM (Zulu 8.52.0.23-CA-macosx) (build 25.282-b08,
>  mixed mode)
> 
>  - Tested secure clusters with TLS ZK, secure Site-to-Site, InvokeHTTP,
>  ListenHTTP
> 
>  On Tue, Feb 2, 2021 at 7:20 PM Joey Frazee   .invalid>
>  wrote:
> 
> > +1 (non-binding)
> >
> > - Verified checksums, signatures, and commit id
> > - Ran builds with Java 1.8 and 11 on Linux and macOS, and validated
> >> RPM
> > build profile
> > - Tested cluster coordination and state management with both embedded
> >>> and
> > external ZooKeepers with TLS enabled and disabled
> > - Verified fix for PutAzureBlobStorage OOME and tested Blob and Queue
> > storage with Azurite emulator
> >
> > -joey
> >
> >> On Feb 2, 2021, at 3:16 PM, Sushil Kumar 
> >> wrote:
> >>
> >> +1 (non-binding) Release this package as nifi-1.13.0
> >>
> >> Deployed this via helm chart(
> >> https://github.com/sushilkm/nifi-chart)
>  on
> >> kubernetes.
> >> Thank you to all the contributors and reviewers.
> >>
> >>
> >>> On Tue, Feb 2, 2021 at 11:02 AM Matt Burgess <
> >> mattyb...@apache.org>
> > wrote:
> >>>
> >>> +1 (binding) Release this package as nifi-1.13.0
> >>>
> >>> Ran through release helper and tried various flows using some of
> >> the
> >>> new features and capabilities added in 1.13.0.  Thanks for RM'ing
> >>> Joe!
> >>>
>  On Mon, Feb 1, 2021 at 8:10 PM Joe Witt 
> >>> wrote:
> 
>  Hello,
> 
>  I am pleased to be calling this vote for the source release of
> >>> Apache
> >>> NiFi
>  1.13.0.
> 
>  The source zip, including signatures, digests, etc. can be found
> >>> at:
> 
>  https://repository.apache.org/content/repositories/orgapachenifi-1176
> 
>  The source being voted upon and the convenience binaries can be
> >>> found
> > at:
>  https://dist.apache.org/repos/dist/dev/nifi/nifi-1.13.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+release+candidate
> 
>  The Git tag is nifi-1.13.0-RC2
>  The Git commit ID is c27e59fc679a2e982102a75b8b8df2b0f062af23
> 
> >>>
> >
> 
> >>>
> >>
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=c27e59fc679a2e982102a75b8b8df2b0f062af23
> 
>  Checksums of 

Re: [VOTE] Release Apache NiFi 1.12.1 (rc2)

[Robert Fellows]

+1 (non-binding)

Ran through the release helper.
Built and ran with Java 11 (OpenJDK Runtime Environment AdoptOpenJDK (build
11.0.8+10))
On Mac OS 10.15.6

Tested a few simple flows.

Thanks for RM'ing, Joe.

-- Rob

On Thu, Sep 24, 2020 at 5:24 PM Matt Burgess  wrote:

> +1 (binding)
>
> Ran through release helper, verified some simple flows, verified
> NIFI-7742 was included. Thanks for handling the release Joe!
>
> On Wed, Sep 23, 2020 at 6:10 PM Joe Witt  wrote:
> >
> > Hello,
> >
> > I am pleased to be calling this vote for the source release of Apache
> NiFi
> > 1.12.1.
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > https://repository.apache.org/content/repositories/orgapachenifi-1170
> >
> > The source being voted upon and the convenience binaries can be found at:
> > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.12.1/
> >
> > 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+release+candidate
> >
> > The Git tag is nifi-1.12.1-RC2
> > The Git commit ID is accfaa3034fa5c3ef55d6402ac31e500247100f9
> >
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=accfaa3034fa5c3ef55d6402ac31e500247100f9
> >
> > Checksums of nifi-1.12.1-source-release.zip:
> > SHA256: 7735c632c6795bb0d299631454bd81006db33d51192cacc1404a5c9779607802
> > SHA512:
> >
> e7f06afc7617df7e3325bce8e34d1d78c4d130c40135661e59ae0eabef50df888759a125dae3ab9556fc940d621c695a50e674ebad8c3066716bfb5fbd27c1c4
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/joewitt.asc
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/release/nifi/KEYS
> >
> > 39 issues were closed/resolved for this release:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12348757
> >
> > Release note highlights can be found here:
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.12.1
> >
> > 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.12.1
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
>


-- 
---
Rob Fellows

Re: [VOTE] Release Apache NiFi 1.12.0

[Robert Fellows]

+ 1 (non-binding)

Ran through the release helper, verified checksums and sigs.
Full build with java 11
Verified basic app usage/functionality.



On Fri, Aug 14, 2020 at 4:04 PM Muazma Zahid  wrote:

>   +1 (non-binding)
> Ran through the release helper. Deployed a 10 node cluster on Azure and
> verified the functionality of new ADLS processors with a standard flow.
> Looks good to me.
>
> Thanks,
> Muazma
>
> On Fri, Aug 14, 2020 at 12:45 PM Andrew Lim 
> wrote:
>
> > +1 (binding)
> >
> > -Ran full clean install on OS X (Catalina 10.15.2)
> > -Tested secure NiFi with secure NiFi Registry 0.7.0
> > -Ran basic flows successfully; tested basic versioned flow functionality
> > -Reviewed documentation updates. Lots of a great additions in this
> release!
> > -Reviewed core UI fixes and improvements. Verified that controller
> > services are searchable [1], but filed a Jira for the navigation to the
> > controller service being broken [2].
> >
> > Drew
> >
> > [1] https://issues.apache.org/jira/browse/NIFI-5925 <
> > https://issues.apache.org/jira/browse/NIFI-5925>
> > [2] https://issues.apache.org/jira/browse/NIFI-7742 <
> > https://issues.apache.org/jira/browse/NIFI-7742>
> >
> > > On Aug 13, 2020, at 4:31 PM, Joe Witt  wrote:
> > >
> > > Hello,
> > >
> > > I am pleased to be calling this vote for the source release of Apache
> > NiFi
> > > 1.12.0.
> > >
> > > The source zip, including signatures, digests, etc. can be found at:
> > > https://repository.apache.org/content/repositories/orgapachenifi-1165
> > >
> > > The source being voted upon and the convenience binaries can be found
> at:
> > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.12.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+release+candidate
> > >
> > > The Git tag is nifi-1.12.0-RC1
> > > The Git commit ID is 4d940bb151eb8d250b0319318b96d23c4a9819ae
> > >
> >
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=4d940bb151eb8d250b0319318b96d23c4a9819ae
> > >
> > > Checksums of nifi-1.12.0-source-release.zip:
> > > SHA256:
> a67ecb34f32cc1f070ebb006b6f05456a2ac663b12f708eadac67754194a6c63
> > > SHA512:
> > >
> >
> 2e04235c4d49a76319af7756289ce11554a412bf5f7dcb6dc3915fc931df9f067142820c297e83bc36cb1079fb8384794ef457a20dd00568761eed6621701953
> > >
> > > Release artifacts are signed with the following key:
> > > https://people.apache.org/keys/committer/joewitt.asc
> > >
> > > KEYS file available here:
> > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > >
> > > 335 issues were closed/resolved for this release:
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12346778
> > >
> > > Release note highlights can be found here:
> > >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.12.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.12.0
> > > [ ] +0 no opinion
> > > [ ] -1 Do not release this package because...
> >
> >
>


-- 
---
Rob Fellows

Re: [VOTE] Release Apache NiFi Registry 0.7.0

[Robert Fellows]

+1 (non-binding)


   - Verified signature
   - Verified the hashes
   - Built and run with java 11
   - Tested basic UI functionality and some REST endpoints.



On Wed, Jul 15, 2020 at 11:32 AM Bryan Bende  wrote:

> Hello,
>
> I am pleased to be calling this vote for the source release of Apache NiFi
> Registry 0.7.0.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1161
>
> The source being voted upon and the convenience binaries can be found at:
>
> https://dist.apache.org/repos/dist/dev/nifi/nifi-registry/nifi-registry-0.7.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+release+candidate
>
> The Git tag is nifi-registry-0.7.0-RC1
> The Git commit ID is c8f26039712354b94c4d458b7ea491316c6facac
>
> https://gitbox.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=c8f26039712354b94c4d458b7ea491316c6facac
>
> Checksums of nifi-registry-0.7.0-source-release.zip:
> SHA256: acc6b21444d229d78b8a604750231e1c7e80495c9cccfb59ec043ebe952fd2a8
> SHA512:
>
> 428839e0c861095547e328fcfda42cb3f2a87c0b03f7205d6878f8b7267975fe2ad051d4b5f980cac8f47a249c8ee21686c8d909f275454e25d8a654099bd683
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/bbende.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 19 issues were closed/resolved for this release:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320920=12346077
>
> Release note highlights can be found here:
>
> https://cwiki.apache.org/confluence/display/NIFIREG/Release+Notes#ReleaseNotes-NiFiRegistry0.7.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-registry-0.7.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>


-- 
---
Rob Fellows

Re: [DISCUSS] rename master branch, look through code for other related issues

[Robert Fellows]

I am a +1 for making the changes.

- Rob Fellows

On Thu, Jun 18, 2020 at 7:52 AM Adam Hunyadi 
wrote:

> 
>
> I propose naming the master branch Voldemort, so that people do not
> speak of its name. Of course this recommendation only applies if noone
> finds choosing the name of a "dark" lord offensive.
>
> 
>
> Adam Hunyadi
>
> On 2020. 06. 18. 12:17, u...@moosheimer.com wrote:
> > Language is always changing and the meaning of words is changing,
> > sometimes positively and sometimes negatively.
> > I think that now is time for change again and we should discuss the use
> > of phrases and meanings.
> >
> > Of course we should change "Master Branch" to "Main Branch".
> > But I also think that we shouldn't just make quick changes because it's
> > opportune and hastily change a few words.
> >
> > An example: We could change Master/Slave to Leader/Follower. This may be
> > a perfect choice for most people in the world.
> > In German Leader is the English word for "Führer". And it is precisely
> > this word that we in Germany do not actually want to use for it.
> >
> > What I mean is that every country and every group (e.g. religion etc.)
> > has its own history and certain words or phrases are just not a perfect
> > choice.
> > We should try to go the ethically correct way worldwide.
> >
> > This concerns the adaptation of current words and phrases with a view to
> > all: in English, Indian, Chinese, German etc. but also for indigenous
> > peoples, different religions etc.
> > And cultural differences should also be taken into account.
> >
> > What I would wish for:
> > Apache.org should set up an "Ethics Board". A group of people of
> > different genders, all colors, religions and from different countries
> > and cultures all over our world.
> > This Ethics Board should find good and for no one discriminating words
> > or phrases for all the areas that stand out today as offensive.
> >
> > And it would be nice if not only computer scientists participated, but
> > also ethicists, philosophers, engineers, various religious people,
> > chemists, biologists, physicists, sociologists, etc.
> >
> > And this Council should set binding targets for all projects.
> >
> > Am 18.06.2020 um 09:36 schrieb Pierre Villard:
> >>> In my perspective this should be an issue for the entire community.
> Being
> >>> able to identify an issue that directly affects another person but not
> >>> one’s self is the definition of privilege. If I can look at how the
> use of
> >>> these words in someone’s daily life or career impacts them negatively,
> >> when
> >>> the change would not harm me at all, I see that as a failure on my
> part. I
> >>> understand the desire to hear from the silent majority, but active
> >>> participation and discussion on the mailing list is the exact measure
> >>> described by the Apache process for participation in the community.
> Those
> >>> who speak here are the ones who will have a voice.
> >> I could not agree more with the above.
> >>
> >> Le jeu. 18 juin 2020 à 04:29, Tony Kurc  a écrit :
> >>
> >>> I suppose I was a bit remiss in not unwinding and/or summarizing some
> of
> >>> what was in that yetus thread to prime the discussion, but a some of
> what
> >>> Andy is mentioning is expanded on a bit in this ietf document [1],
> which is
> >>> linked in one of the articles.
> >>>
> >>> 1. https://tools.ietf.org/id/draft-knodel-terminology-00.html
> >>>
> >>>
> >>> On Wed, Jun 17, 2020, 10:02 PM Andy LoPresto 
> wrote:
> >>>
>  Hi Edward, thanks for sharing your thoughts. I’ll reply inline.
> 
> > - Some of the terms proposed are not industry standard and may
>  potentially
> > cause significant issue for non-english speakers.
>  I actually believe making these changes will _improve_ the clarity for
>  non-english speakers. “Whitelist” and “blacklist” confer no inherent
> >>> reason
>  to mean allow and deny other than connotative biases. “Allow” and
> “deny”
>  explicitly indicate the verb that is happening. Another example is
> branch
>  naming. “Masters” don’t have “branches”. “Trunks” do. These terms make
>  _more_ sense for a non-English speaker than the current terms.
> 
> > - For each change that is made can we guarantee that we will not lose
> > clarity of meaning, and then have revert the change down the line if
> >>> the
> > change causes a drop in usage.
>  I don’t expect the community will opt to change the new terms back to
> >>> ones
>  with negative connotations in the future. If there is discussion about
> >>> it,
>  this thread will provide good historical context for why the decision
> was
>  made to change it, just as the mailing list discussions do for other
> code
>  changes.
> 
> > - Of what percentage of people is this truly an issue for and what
> > percentage isn't. Any change that has the potential to cause a major
>  split
> > in the community, there must be as close as 

Re: [VOTE] Release Apache NiFi Registry 0.6.0

[Robert Fellows]

+1 (non-binding)

Verified hashes.
Built and ran (unsecured) with Java 11.
Exercised the REST API to create buckets and versioned flows.
Quickly tested the UI.



On Thu, Apr 2, 2020 at 4:54 PM Nathan Gough  wrote:

> +1 (non-binding)
>
> Built with tests, connected a secured nifi to a secured registry. Connected
> NiFi LDAP, logged in and out with LDAP and tested API to confirm the token
> is invalidated as expected. Version controlled a simple flow.
>
> On Thu, Apr 2, 2020 at 4:09 PM Aldrin Piri  wrote:
>
> > I am of the opinion it is only a minor nuisance.  As it is an arg, it is
> > easily overridden on build (this issue is also present on the Docker Hub
> > item).  The script I use to publish images  explicitly provides the
> version
> > arg and would not preclude us from having an appropriately versioned
> image.
> >
> > On Thu, Apr 2, 2020 at 4:01 PM Chris Sampson
> >  wrote:
> >
> > > Is it a problem that you're building 0.6.0 but the docker image is
> > > configured for 1.0.0 (
> > >
> > >
> >
> https://github.com/apache/nifi-registry/blob/master/nifi-registry-docker-maven/dockermaven/Dockerfile
> > > )
> > > as per
> > >
> https://issues.apache.org/jira/plugins/servlet/mobile#issue/NIFIREG-338?
> > >
> > >
> > >
> > > Cheers,
> > >
> > > Chris Sampson
> > >
> > > On Thu, 2 Apr 2020, 19:00 Marton Szasz,  wrote:
> > >
> > > > +1 (non-binding)
> > > >
> > > > Went through the helper guide with the correct commit ID and verified
> > the
> > > > release against a minifi c++ instance.
> > > >
> > > > Thanks,
> > > > Marton
> > > >
> > > > On Thu, 2 Apr 2020 at 18:51, Arpad Boda 
> > > > wrote:
> > > >
> > > > > Thanks for pointing that out, I copied wrong ID.
> > > > >
> > > > > The correct commit ID is: 4ddfde57f0163baa08eb782fc8be9c51d8f58af7
> > > > >
> > > > >
> > > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=4ddfde57f0163baa08eb782fc8be9c51d8f58af7
> > > > > That's the commit associated with the RC tag.
> > > > >
> > > > > Dev,
> > > > > please use this commit ID for the release verification.
> > > > >
> > > > > Thanks,
> > > > > Arpad
> > > > >
> > > > >
> > > > >
> > > > > On Thu, Apr 2, 2020 at 6:41 PM Joe Witt 
> wrote:
> > > > >
> > > > > > +1 (binding)
> > > > > >
> > > > > > Did the usual checks and ran a live nifi against it which worked
> > > > > > perfectly.  Did not do secured instances though.
> > > > > >
> > > > > > Arpdad: You want to clarify the commit that the source release is
> > > based
> > > > > on
> > > > > > is
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=4ddfde57f0163baa08eb782fc8be9c51d8f58af7
> > > > > >
> > > > > > That is the parent of the one you sent which has 0.6.1-SNAPSHOT.
> > > > > >
> > > > > > Thanks
> > > > > > Joe
> > > > > >
> > > > > > On Thu, Apr 2, 2020 at 11:54 AM Arpad Boda 
> > wrote:
> > > > > >
> > > > > > > Hello,
> > > > > > >
> > > > > > > I am pleased to be calling this vote for the source release of
> > > Apache
> > > > > > > NiFi Registry nifi-registry-0.6.0.
> > > > > > >
> > > > > > > The source zip, including signatures, digests, etc. can be
> found
> > > at:
> > > > > > >
> > > >
> https://repository.apache.org/content/repositories/orgapachenifi-1160
> > > > > > >
> > > > > > > The Git tag is nifi-registry-0.6.0-RC1
> > > > > > > The Git commit ID is ed5c9b3f2faa8b1cab18f157b7d3263dae289aae
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=ed5c9b3f2faa8b1cab18f157b7d3263dae289aae
> > > > > > >
> > > > > > > Checksums of nifi-registry-0.6.0-source-release.zip:
> > > > > > > SHA256:
> > > > > 0ed06ef762588be0154207932d2d1ebd1266c45aed299d0fb170cbeabd4c6e2b
> > > > > > > SHA512:
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> aa1f03c20902bf9cd94574e45cbd57526763ab135421e9d1df489cac7c487cb9c6d20ba3f6a74d7ae37b97a7de71d12edbc1c9fabf6d6b29f29397164011e097
> > > > > > >
> > > > > > > Release artifacts are signed with the following key:
> > > > > > > https://people.apache.org/keys/committer/aboda.asc
> > > > > > >
> > > > > > > KEYS file available here:
> > > > > > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > > > > > >
> > > > > > > 40 issues were closed/resolved for this release:
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320920=12347009
> > > > > > >
> > > > > > > Release note highlights can be found here:
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/NIFIREG/Release+Notes#ReleaseNotes-NiFiRegistry0.6.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.
> > > > > > >

Re: [VOTE] Release Apache NiFi 1.11.3

[Robert Fellows]

+1 (non-binding)

Ran through the release checklist, verified signature and hashes.
Built with OpenJDK 11.0.4 (Zulu)
Ran a few basic flows
Quick check of parameter functionality

Looks Good, Thanks for RM'ing Joe!

- Rob

On Sun, Feb 23, 2020 at 12:10 AM Chad Zobrisky  wrote:

> +1 non-binding.
> Ran through verify release checklist and everything was as expected.
>
> Ran the PutDistributedMapCache flow uploaded to the issue and had no issues
> with open file growth after 4 hours of running.
>
> Looks good, great turn around. Thanks For RMing Joe.
>
> Chad
>
> On Sat, Feb 22, 2020 at 9:01 PM Mike Thomsen 
> wrote:
>
> > +1 binding. Set up a site to site provenance reporting task with a flow
> > that generated a high volume of junk data. Didn't see any signs of the
> > reported bug.
> >
> > On Sat, Feb 22, 2020 at 3:21 AM Joe Witt  wrote:
> >
> > > Hello,
> > >
> > > I am pleased to be calling this vote for the source release of Apache
> > NiFi
> > > 1.11.3.
> > >
> > > The source zip, including signatures, digests, etc. can be found at:
> > > https://repository.apache.org/content/repositories/orgapachenifi-1158
> > >
> > > The source being voted upon and the convenience binaries can be found
> at:
> > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.11.3/
> > >
> > > 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+release+candidate
> > >
> > > The Git tag is nifi-1.11.3-RC1
> > > The Git commit ID is 10b509cf5bb88b12b0dd497543291f3c49a9903f
> > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=10b509cf5bb88b12b0dd497543291f3c49a9903f
> > >
> > > Checksums of nifi-1.11.3-source-release.zip:
> > > SHA256:
> b2544719a8de02892b3436f1e6084b9b6011bf706a183fa2f059a9961634a7bd
> > > SHA512:
> > >
> > >
> >
> 353671e06dd60e186d2a9a29eb9b7c2d183757f6a0f76801b4ecb5d87aab99e701b9ebde932ee414d4b304afd2bd1d0a0e574906a385cfafc8de36cc47c2d0a3
> > >
> > > Release artifacts are signed with the following key:
> > > https://people.apache.org/keys/committer/joewitt.asc
> > >
> > > KEYS file available here:
> > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > >
> > > 14 issues were closed/resolved for this release:
> > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12347022
> > >
> > > Release note highlights can be found here:
> > >
> > >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.11.3
> > >
> > > 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.11.3
> > > [ ] +0 no opinion
> > > [ ] -1 Do not release this package because...
> > >
> >
>


-- 
---
Rob Fellows

Re: [VOTE] Release Apache NiFi 1.11.2 (rc1)

[Robert Fellows]

+1 (non-binding)

* verified sigs and hashes
* full build on java 11
* tested a few processors, basic functionality.

Thanks for RM'ing, Joe!



On Tue, Feb 18, 2020 at 2:31 PM Matt Gilman  wrote:

> +1 (binding)
>
> - Check signatures and hashes
> - Full build
> - Verified some of the JIRAs addressed in this release
>
> Thanks for RMing Joe!
>
> On Tue, Feb 18, 2020 at 2:01 PM Matt Burgess  wrote:
>
> > +1 (binding) ran through release helper and various flows. Thanks Joe
> > for RM'ing!
> >
> > On Fri, Feb 14, 2020 at 10:15 PM Joe Witt  wrote:
> > >
> > > Hello,
> > >
> > > I am pleased to be calling this vote for the source release of Apache
> > NiFi
> > > 1.11.2.
> > >
> > > The source zip, including signatures, digests, etc. can be found at:
> > > https://repository.apache.org/content/repositories/orgapachenifi-1157
> > >
> > > The source being voted upon and the convenience binaries can be found
> at:
> > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.11.2/
> > >
> > > 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+release+candidate
> > >
> > > The Git tag is nifi-1.11.2-RC1
> > > The Git commit ID is 6d2ec87c8a46d5d39f3b4683e4ea9dec91138d52
> > >
> >
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=6d2ec87c8a46d5d39f3b4683e4ea9dec91138d52
> > >
> > > Checksums of nifi-1.11.2-source-release.zip:
> > > SHA256:
> 2a030956a7cc9578e616195dd4cf8a853976e17eb040a7b216f844ae2ce9a610
> > > SHA512:
> > >
> >
> 135101f3f9b37b559e850e79c89bad36d707126fcea559fa4f6846c4cb21c17ab51c119c5005df359a4d3a066c66611b00816c2f7586b24d34f0f418d4b5c527
> > >
> > > Release artifacts are signed with the following key:
> > > https://people.apache.org/keys/committer/joewitt.asc
> > >
> > > KEYS file available here:
> > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > >
> > > 14 issues were closed/resolved for this release:
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12346972
> > >
> > > Release note highlights can be found here:
> > >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.11.2
> > >
> > > 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.11.2
> > > [ ] +0 no opinion
> > > [ ] -1 Do not release this package because...
> >
>


-- 
---
Rob Fellows

Re: [VOTE] Release Apache NiFi 1.11.1 (rc1)

[Robert Fellows]

+1 (non-binding)

Verified signatures and hashes
Built and run on MacOS with Java 11 (OpenJDK Runtime Environment
Zulu11.33+15-CA (build 11.0.4+11-LTS))
Built and ran some simple flows
Verified some of the bugs fixed (NIFI-7032, NIFI-7069)

One minor thing that shouldn't hold the release IMO...
Built with java 8 and was able to verify NIFI-7080. When building with java
11, this does not work since the docker image is based off of "openjdk:8-jre",
the binaries built with java 11 fail.

--Rob Fellows



On Mon, Feb 3, 2020 at 6:28 AM Marc Parisi  wrote:

> +1 binding
>
>  Verified sigs, hashes, etc per the typical release helper process.
>
>   Since the list of resolved issues were so small I verified most, with the
> exception of 7051, 7080, and 7069. All others appear to be resolved.
>   Only built on PopOS and Centos due to superbowl -- but everything looks
> good.
>
>
> On Mon, Feb 3, 2020 at 4:04 AM Yoshiaki Takahashi 
> wrote:
>
> > +1 (non-binding)
> >
> > - [x] Non-RPM (usual) build with Java 8.
> > - [x] Deploy on 3 node secured cluster in CentOS 7.7.0 and run on Java 8.
> > - [x] Non-RPM (usual) build with Java 11.
> > - [x] Deploy on 1 node non secured cluster in CentOS 7.7.0 and run on
> Java
> > 11.
> >
> > Thanks for working for the release!
> >
> > On 2020/01/31 20:11:00, Joe Witt  wrote:
> > > Hello,
> > >
> > > I am pleased to be calling this vote for the source release of Apache
> > NiFi
> > > 1.11.1.
> > >
> > > The source zip, including signatures, digests, etc. can be found at:
> > > https://repository.apache.org/content/repositories/orgapachenifi-1156
> > >
> > > The source being voted upon and the convenience binaries can be found
> at:
> > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.11.1/
> > >
> > > 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+release+candidate
> > >
> > > The Git tag is nifi-1.11.1-RC1
> > > The Git commit ID is d22858d045fb3e5343a87d362855810963aa8556
> > >
> >
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=d22858d045fb3e5343a87d362855810963aa8556
> > >
> > > Checksums of nifi-1.11.1-source-release.zip:
> > > SHA256:
> 41878981689e08c51ed7bb921c46f6328c1e6b6c94460a2382069bd042ab7112
> > > SHA512:
> > >
> >
> d309342732196225ffdbac3eaeed3c9b949bcee00509fb6d073618d869c6db56b426f5867849a8ae752d7acc8c6dd18a14cb377655774d86f91d736350eb2041
> > >
> > > Release artifacts are signed with the following key:
> > > https://people.apache.org/keys/committer/joewitt.asc
> > >
> > > KEYS file available here:
> > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > >
> > > 9 issues were closed/resolved for this release:
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12346906
> > >
> > > Release note highlights can be found here:
> > >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.11.1
> > >
> > > 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.11.1
> > > [ ] +0 no opinion
> > > [ ] -1 Do not release this package because...
> > >
> >
>


-- 
---
Rob Fellows

Re: Parameters within password/passphrase fields

[Robert Fellows]

Chris,
  I was able to reproduce your issue so I just logged the issue. You can
track it here: https://issues.apache.org/jira/browse/NIFI-6868. Feel free
to add any more context/comments as you like.

- Rob

On Wed, Nov 13, 2019 at 3:55 PM Robert Fellows 
wrote:

> Chris,
>   I think there are 2 things happening here. First, I think there might be
> a bug in how sensitive parameters are evaluated on the backend and it is
> causing your issue. Please log an issue for this.
>
> Second, the UI is a bit confusing in terms of the availability of the
> "Convert to parameter" and "Go to Parameter" actions for sensitive
> parameter references in properties. However, this is due to the nature of
> sensitive parameters/properties. The actual value of the sensitive property
> is only ever known to the UI when the user enters the value. Once applied,
> those values are never sent back to the UI. The UI knows there is a value
> set, but it has no idea if it contains a parameter reference or not. The
> "Go To Parameter" action is only available when the UI can parse the value
> of the property and it matches the '#{...}' syntax format. Since the values
> is not sent to the UI, it can't parse the value to know if it is a
> parameter reference or not. The "Convert to parameter" action option is
> available just as a shortcut to create a new parameter, it is hidden when
> it is known that the value already references a parameter. This may be
> improved in the future, but it was implemented this way intentionally.
>
> - Rob
>
> On Wed, Nov 13, 2019 at 11:17 AM Chris Lundeberg 
> wrote:
>
>> Hi all,
>>
>> Recently we upgraded to Nifi 1.10 to take advantage of parameters and
>> using
>> those within our deployment process (using the registry).  I am seeing
>> some
>> strange behavior and want to confirm my understanding of how this new
>> feature works, before digging deeper.
>>
>> *Some general background info:*
>> I have a three node cluster running Nifi 1.10.  Its security enabled, but
>> I
>> am using an admin user with full rights to view/modify policies.  Its
>> running on linux and using java 8.
>>
>> *Producing the issue:*
>> As a test, I moved over some existing flows from our 1.9.2 cluster (same
>> specs and user rights as we build everything with puppet).  A few of the
>> processors are pulling and pushing to SFTP, for which we use an RSA key, a
>> known hosts file and the "paraphrase" property descriptor is populated
>> with
>> a password.  I converted that password over to a parameter within the
>> master processor group, set the "Process Group Parameter Context" for the
>> processor group this processor resides and saved everything.  After that
>> was done, I was able to access the parameter within #{ + ctrl + space.  I
>> choose the correct one, closed in the curly braces and saved the
>> processor.  I noticed immediately after saving and re-opening that the new
>> options icon to the right of the property descriptor reverted back from
>> "access the parameters" to "convert to a parameter".  I didn't think much
>> of it, besides maybe a small bug in the UI (Although that does save
>> correctly when you set a non sensitive field).  When I started the
>> processor, it immediately failed with an authentication error. I tried
>> setting a few different parameters, manually typing in #{ftp.password}
>> into
>> the paraphrase and even setting a new parameter directly from the helper
>> icon within the processor.  That didn't seem to change the behavior.
>>  Lastly I went back into the processor and removed the "Sensitive value
>> set" and typed the password in plain text and saved.  It worked fine after
>> that.
>>
>> I thought it may have been something off with our policies or even
>> install,
>> so I installed Nifi locally and experienced the same issue. It seems as
>> though the actual value is not being evaluated correctly when passed
>> into/through the processor for sensitive values.
>>
>> Has anyone experienced this before?
>>
>> Thanks!
>>
>> Chris Lundeberg
>>
>
>
> --
> ---
> Rob Fellows
>


-- 
---
Rob Fellows

Re: Parameters within password/passphrase fields

[Robert Fellows]

Chris,
  I think there are 2 things happening here. First, I think there might be
a bug in how sensitive parameters are evaluated on the backend and it is
causing your issue. Please log an issue for this.

Second, the UI is a bit confusing in terms of the availability of the
"Convert to parameter" and "Go to Parameter" actions for sensitive
parameter references in properties. However, this is due to the nature of
sensitive parameters/properties. The actual value of the sensitive property
is only ever known to the UI when the user enters the value. Once applied,
those values are never sent back to the UI. The UI knows there is a value
set, but it has no idea if it contains a parameter reference or not. The
"Go To Parameter" action is only available when the UI can parse the value
of the property and it matches the '#{...}' syntax format. Since the values
is not sent to the UI, it can't parse the value to know if it is a
parameter reference or not. The "Convert to parameter" action option is
available just as a shortcut to create a new parameter, it is hidden when
it is known that the value already references a parameter. This may be
improved in the future, but it was implemented this way intentionally.

- Rob

On Wed, Nov 13, 2019 at 11:17 AM Chris Lundeberg 
wrote:

> Hi all,
>
> Recently we upgraded to Nifi 1.10 to take advantage of parameters and using
> those within our deployment process (using the registry).  I am seeing some
> strange behavior and want to confirm my understanding of how this new
> feature works, before digging deeper.
>
> *Some general background info:*
> I have a three node cluster running Nifi 1.10.  Its security enabled, but I
> am using an admin user with full rights to view/modify policies.  Its
> running on linux and using java 8.
>
> *Producing the issue:*
> As a test, I moved over some existing flows from our 1.9.2 cluster (same
> specs and user rights as we build everything with puppet).  A few of the
> processors are pulling and pushing to SFTP, for which we use an RSA key, a
> known hosts file and the "paraphrase" property descriptor is populated with
> a password.  I converted that password over to a parameter within the
> master processor group, set the "Process Group Parameter Context" for the
> processor group this processor resides and saved everything.  After that
> was done, I was able to access the parameter within #{ + ctrl + space.  I
> choose the correct one, closed in the curly braces and saved the
> processor.  I noticed immediately after saving and re-opening that the new
> options icon to the right of the property descriptor reverted back from
> "access the parameters" to "convert to a parameter".  I didn't think much
> of it, besides maybe a small bug in the UI (Although that does save
> correctly when you set a non sensitive field).  When I started the
> processor, it immediately failed with an authentication error. I tried
> setting a few different parameters, manually typing in #{ftp.password} into
> the paraphrase and even setting a new parameter directly from the helper
> icon within the processor.  That didn't seem to change the behavior.
>  Lastly I went back into the processor and removed the "Sensitive value
> set" and typed the password in plain text and saved.  It worked fine after
> that.
>
> I thought it may have been something off with our policies or even install,
> so I installed Nifi locally and experienced the same issue. It seems as
> though the actual value is not being evaluated correctly when passed
> into/through the processor for sensitive values.
>
> Has anyone experienced this before?
>
> Thanks!
>
> Chris Lundeberg
>


-- 
---
Rob Fellows

Re: [VOTE] Release Apache NiFi 1.10.0 (rc3)

[Robert Fellows]

+1 (non-binding)

[X] Verified the checksums
[X] Verified signature
[X] Verify build (java 11)
[X] Verify general functionality (including parameter contexts and
back-pressure prediction UI)

On Thu, Oct 31, 2019 at 10:00 AM Peter Turcsanyi 
wrote:

> +1 (non-binding)
>
> Verified checksums and signatures.
> Built source with empty Maven repo (tests ok, contrib-check ok).
> Tested some flows (all AWS processors, focusing on the new S3 features:
> encryption, storage classes, requester pays).
>
> Peter
>
> On Thu, Oct 31, 2019 at 2:28 PM Bryan Bende  wrote:
>
> > +1 (binding)
> >
> > Everything in release helper checked out. I did run into a test
> > failure the first time building the source, but then trying again
> > succeeded. I think it is a sporadic failure we have seen before...
> >
> > [ERROR] Tests run: 8, Failures: 1, Errors: 0, Skipped: 0, Time
> > elapsed: 1.415 s <<< FAILURE! - in
> > org.apache.nifi.wali.TestLengthDelimitedJournal
> > [ERROR]
> >
> testFailureDuringWriteCannotCauseCorruption(org.apache.nifi.wali.TestLengthDelimitedJournal)
> >  Time elapsed: 1.022 s  <<< FAILURE!
> > java.lang.AssertionError: expected:<0> but was:<2>
> > at
> >
> org.apache.nifi.wali.TestLengthDelimitedJournal.testFailureDuringWriteCannotCauseCorruption(TestLengthDelimitedJournal.java:585)
> >
> > On Thu, Oct 31, 2019 at 6:42 AM Kotaro Terada 
> wrote:
> > >
> > > Thanks for taking care of it, Pierre and Joe!
> > >
> > > > Please note only PMC votes are binding.
> > >
> > > I got it,  I'll be careful next time.
> > >
> > > Thanks,
> > > Kotaro
> > >
> > >
> > > On Thu, Oct 31, 2019 at 7:32 PM Joe Witt  wrote:
> > >
> > > > Id just flag this on release notes and we can fix for the next
> release.
> > > >
> > > > Kotaro good find.  Please note only PMC votes are binding.
> > > >
> > > > Thanks
> > > >
> > > > On Thu, Oct 31, 2019 at 6:27 AM Pierre Villard <
> > > > pierre.villard...@gmail.com>
> > > > wrote:
> > > >
> > > > > Good catch Kotaro! I merged the fix for #2. The fix for #1 LGTM but
> > I'll
> > > > > let the guys who worked on the Java 11 bits look into it.
> > > > >
> > > > > Joe, I didn't set the fix version on the JIRA and will wait until
> we
> > > > reach
> > > > > a decision regarding this RC.
> > > > >
> > > > > Le jeu. 31 oct. 2019 à 11:08, Kotaro Terada  a
> > > > écrit :
> > > > >
> > > > > > -1 (binding), due to the following problems I found.
> > > > > >
> > > > > > (1) NiFi doesn't start up from the rpm build on Java 11.
> > > > > >
> > > > > > We have a mismatch in the "lib" directories of rpm and non-rpm
> > build.
> > > > > This
> > > > > > causes that NiFi (with Java 11) doesn't start up from the rpm
> > build.
> > > > Some
> > > > > > jar files should be located in the "lib/bootstrap/" but they are
> > > > > currently
> > > > > > in "lib/".
> > > > > >
> > > > > > I checked the following behaviors:
> > > > > > - Non-RPM (usual) build with Java 8 and run on Java 8... OK
> > > > > > - Non-RPM (usual) build with Java 11 and run on Java 11... OK
> > > > > > - RPM build with Java 8 and run on Java 8... OK (isn't affected
> by
> > the
> > > > > lib
> > > > > > mismatch)
> > > > > > - RPM build with Java 11 and run on Java 11... NiFi doesn't start
> > (this
> > > > > > problem)
> > > > > >
> > > > > > I created a JIRA and a PR to fix it:
> > > > > > https://issues.apache.org/jira/browse/NIFI-6827
> > > > > >
> > > > > > (2) There is an unintentional string in "conf/logback.xml".
> > > > > >
> > > > > > The "conf/logback.xml" seems to have an unintentional string
> > > > > > "MockProcessContext". I guess this was slipped into it by the
> > merging
> > > > > > commit of https://github.com/apache/nifi/pull/3773
> > unintentionally.
> > > > > >
> > > > > > I created a JIRA and a PR to fix it:
> > > > > > https://issues.apache.org/jira/browse/NIFI-6828
> > > > > >
> > > > > > Could you take a look at them, please?
> > > > > >
> > > > > > Thanks for working for the release!
> > > > > > Kotaro
> > > > > >
> > > > > >
> > > > > > On Thu, Oct 31, 2019 at 6:10 PM Pierre Villard <
> > > > > > pierre.villard...@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > +1 (binding)
> > > > > > >
> > > > > > > Went through the release helper guide and it LGTM. Deployed
> > > > > > > secured/unsecured standalone/cluster instances on Google Cloud
> > with
> > > > > > various
> > > > > > > flows including the new BigQuery processor and everything is
> > looking
> > > > > > good.
> > > > > > >
> > > > > > > Thanks Joe for taking care of the release!
> > > > > > >
> > > > > > > Pierre
> > > > > > >
> > > > > > > Le jeu. 31 oct. 2019 à 03:12, Shayne Burgess <
> > > > shayne.burg...@gmail.com
> > > > > >
> > > > > > a
> > > > > > > écrit :
> > > > > > >
> > > > > > > > +1 (non-binding)
> > > > > > > >
> > > > > > > > Deployed cluster in Azure and smoke tested a fairly
> complicated
> > > > data
> > > > > > > flow.
> > > > > > > >
> > > > > > > > Verified the fixes for the Azure EventHub Processor that were
> 

Re: New Contribution

[Robert Fellows]

There is a new feature in the works that might help you out:

https://cwiki.apache.org/confluence/display/NIFI/Better+Support+for+Parameterizing+Flows

https://issues.apache.org/jira/browse/NIFI-6276

This will be available in 1.10 which isn’t that far out if you can wait.


On Fri, Sep 27, 2019 at 4:02 PM Andrew Glassman 
wrote:

> Hello,
>
> I've been using NiFi, and really like the platform.  I may have some
> contributions, but wanted to make sure there wasn't a way to achieve what
> I'm looking to do before creating a ticket, and possibly coding the
> feature.
>
> I've been using the Publish/ConsumeKafka_X_X  processors with Confluent
> Cloud.  In order to configure the processors to connect, I had to use the
> following dynamic properties:
>
> request.time.out.ms
> retry.backoff.ms
> sasl.jaas.config
> sasl.mechanism
> ssl.endpoint.identification.algorithm
>
> I have multiple Publish and Consume processors per ProcessGroup.  I'd like
> to be able to use ProcessGroup variables so that I can set these
> configurations in one spot.  Unfortunately, the dynamic properties for
> these processors does not support expression language variable replacement.
>
> Should I start working on getting this supported, or is there something I'm
> missing?
>
> Thanks,
>
> Andy Glassman
>
-- 
---
Rob Fellows

Re: [VOTE] Release Apache NiFi Registry 0.5.0

[Robert Fellows]

+1 non-binding

* Downloaded and imported KEYS
* Downloaded release artifacts
* Verified signatures and hashes
* Built from source with "-Pcontrib-check" (not a clean maven repo, however)
* Verified LICENSE, NOTICE, and README are present in source and assembly
generated
* Ran the binary (both non-secured and secured configurations)
  * Used the TestRestAPI helper class to import some buckets and flows
  * Tested various parts of the UI.
* Works as expected




On Wed, Aug 21, 2019 at 2:31 PM Bryan Bende  wrote:

> Hello,
>
> I am pleased to be calling this vote for the source release of Apache
> NiFi Registry nifi-registry-0.5.0.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1147
>
> The Git tag is nifi-registry-0.5.0-RC1
> The Git commit ID is 8a1901e79b8bb6ef310a9c7d8bf59a3e34b41d16
>
> https://gitbox.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=8a1901e79b8bb6ef310a9c7d8bf59a3e34b41d16
>
> Checksums of nifi-registry-0.5.0-source-release.zip:
> SHA256: 804948c2f3d6d32f88c37c1827d1c9c2d1f842f0ef7e7d953d24e76b152a093b
> SHA512:
> 0ae202b64ad3b3ab3dadb71b9dea210ac4c8eb1cf3922f10a71d175df75ec069e8a039bcc961d1969a6ac7417da4cc5bd4d0cc1e8515d88be6bd55b7c8c9bce9
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/bbende.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 28 issues were closed/resolved for this release:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320920=12345561
>
> Release note highlights can be found here:
>
> https://cwiki.apache.org/confluence/display/NIFIREG/Release+Notes#ReleaseNotes-NiFiRegistry0.5.0
>
> The vote will be open for 72 hours.
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test.
> Then please vote:
>
> [ ] +1 Release this package as nifi-registry-0.5.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>


-- 
---
Rob Fellows

Re: Re:[EXT] [DISCUSS] Predictive Analytics for NiFi Metrics

[Robert Fellows]

Mark and Yolanda,
  I submitted the PR I mentioned yesterday for the UI changes that surface
the exposed prediction data. Let me know what you think.

https://github.com/apache/nifi/pull/3660

Thanks,
Rob


On Mon, Aug 19, 2019 at 4:17 PM Yolanda Davis 
wrote:

> Hi Mark and Rob
>
> Mark thanks so much for the info on your work and Rob thanks for jumping in
> on the UI! I just wanted to add, Mark, that looking at your branch I think
> we also may have some opportunities to exchange notes or collaborate on the
> backend as well.  The work in the feature branch is still in progress (with
> some decoupling to ensure we can allow flexible configuration of models).
> Please feel free to review and leave comments under the parent JIRA.  At
> the same time I'll take a deeper dive on your branch and perhaps we can
> exchange notes on potential areas for improvement/collaboration if it makes
> sense?
>
> Thanks Again,
>
> -yolanda
>
>
> On Mon, Aug 19, 2019 at 3:34 PM Robert Fellows 
> wrote:
>
> > Hey Mark,
> >   I've started working on some UI based on the initial commit for this
> > proposal. What you have done and what I am working on have a bit of
> > overlap, but not much.
> > I'm working on getting the predicted count and bytes into the existing
> > connection metric display that is already on the canvas. The only overlap
> > looks like it might be in the
> > Summary table. I plan on adding a PR for my additions hopefully tomorrow.
> > Maybe once it is up we can discuss how we bring the them together where
> it
> > makes sense?
> >
> > This is the main JIRA case:
> > https://issues.apache.org/jira/browse/NIFI-6510
> > And this is the subtask that I am working toward:
> > https://issues.apache.org/jira/browse/NIFI-6568
> >
> >
> > -- Rob Fellows
> >
> > On Mon, Aug 19, 2019 at 2:26 PM Owens, Mark 
> wrote:
> >
> > > The images from the preview email do not appear to be displaying. They
> > can
> > > be viewed at:
> > > https://github.com/jmark99/nifi-images
> > >
> > > From: Owens, Mark 
> > > Sent: Monday, August 19, 2019 2:25 PM
> > > To: dev@nifi.apache.org
> > > Subject: RE: Re:[EXT] [DISCUSS] Predictive Analytics for NiFi Metrics
> > >
> > >
> > > Hi Yolanda,
> > >
> > >
> > >
> > > I've been working on a feature that appears to possibly overlap with
> the
> > > work you are pursuing. Perhaps we should see if/should we try to
> > coordinate
> > > our efforts. I've been updating NiFi to predict the time to queue
> > overflow
> > > for both flowfiles and bytes and displaying that information in the
> GUI.
> > > For the initial attempt, I’ve been using a simple model of straight
> line
> > > prediction over a sliding window of 15 minutes to predict when flows
> will
> > > fail. This estimate is then displayed on both the NiFi Summary page
> under
> > > the connections tab and in the status history graphs.  Below are
> examples
> > > of what would be displayed to the user.
> > >
> > >
> > >
> > > [cid:image001.png@01D55696.E4CCD550]
> > >
> > >
> > >
> > > The Connection tab contains a new column on the right that displays the
> > > prediction for both flow files and data size. The user can select a
> > maximum
> > > time at which specific times are no longer displayed. In this example,
> if
> > > the prediction lies beyond 12 hours then the display simply indicates
> > that
> > > the flow is greater than 12 hours away from failure at the moment.
> > >
> > >
> > >
> > > [cid:image002.png@01D55697.2C8AC500]
> > >
> > >
> > >
> > > This display graphs the prediction for byte overflow over time. Note
> that
> > > if the estimate is greater than the user provided maximum value of
> > interest
> > > the graph maxes out at that time, effectively indicating no overflow
> > > concerns.
> > >
> > >
> > >
> > > [cid:image003.png@01D55697.965C27D0]
> > >
> > >
> > >
> > > A similar display for flowfile count is displayed as well.
> > >
> > >
> > >
> > > The current state of work can be found at
> > > https://github.com/jmark99/nifi/tree/time-to-overflow
> > >
> > >
> > >
> > > I welcome your (or any others) feedback on this effort.
> > >
> > >
> > >
> > > Thanks,
>

Re: Re:[EXT] [DISCUSS] Predictive Analytics for NiFi Metrics

[Robert Fellows]

Hey Mark,
  I've started working on some UI based on the initial commit for this
proposal. What you have done and what I am working on have a bit of
overlap, but not much.
I'm working on getting the predicted count and bytes into the existing
connection metric display that is already on the canvas. The only overlap
looks like it might be in the
Summary table. I plan on adding a PR for my additions hopefully tomorrow.
Maybe once it is up we can discuss how we bring the them together where it
makes sense?

This is the main JIRA case: https://issues.apache.org/jira/browse/NIFI-6510
And this is the subtask that I am working toward:
https://issues.apache.org/jira/browse/NIFI-6568


-- Rob Fellows

On Mon, Aug 19, 2019 at 2:26 PM Owens, Mark  wrote:

> The images from the preview email do not appear to be displaying. They can
> be viewed at:
> https://github.com/jmark99/nifi-images
>
> From: Owens, Mark 
> Sent: Monday, August 19, 2019 2:25 PM
> To: dev@nifi.apache.org
> Subject: RE: Re:[EXT] [DISCUSS] Predictive Analytics for NiFi Metrics
>
>
> Hi Yolanda,
>
>
>
> I've been working on a feature that appears to possibly overlap with the
> work you are pursuing. Perhaps we should see if/should we try to coordinate
> our efforts. I've been updating NiFi to predict the time to queue overflow
> for both flowfiles and bytes and displaying that information in the GUI.
> For the initial attempt, I’ve been using a simple model of straight line
> prediction over a sliding window of 15 minutes to predict when flows will
> fail. This estimate is then displayed on both the NiFi Summary page under
> the connections tab and in the status history graphs.  Below are examples
> of what would be displayed to the user.
>
>
>
> [cid:image001.png@01D55696.E4CCD550]
>
>
>
> The Connection tab contains a new column on the right that displays the
> prediction for both flow files and data size. The user can select a maximum
> time at which specific times are no longer displayed. In this example, if
> the prediction lies beyond 12 hours then the display simply indicates that
> the flow is greater than 12 hours away from failure at the moment.
>
>
>
> [cid:image002.png@01D55697.2C8AC500]
>
>
>
> This display graphs the prediction for byte overflow over time. Note that
> if the estimate is greater than the user provided maximum value of interest
> the graph maxes out at that time, effectively indicating no overflow
> concerns.
>
>
>
> [cid:image003.png@01D55697.965C27D0]
>
>
>
> A similar display for flowfile count is displayed as well.
>
>
>
> The current state of work can be found at
> https://github.com/jmark99/nifi/tree/time-to-overflow
>
>
>
> I welcome your (or any others) feedback on this effort.
>
>
>
> Thanks,
> Mark
>
>
>
> P.S. If the images are not displaying, they can be viewed at
> https://github.com/jmark99/nifi-images
>
>
>
>
>
>
>
> -Original Message-
> From: Yolanda Davis  yolanda.m.da...@gmail.com>>
> Sent: Monday, August 19, 2019 11:29 AM
> To: dev@nifi.apache.org
> Subject: Re:[EXT] [DISCUSS] Predictive Analytics for NiFi Metrics
>
>
>
> Hello All,
>
>
>
> I just wanted to follow up on the discussion we started a couple of weeks
> ago concerning an analytics framework for NiFi metrics.  Working with Andy
> Christianson and Matt Burgess we shaped our ideas and drafted a proposal
> for this feature on the Apache NiFi Wiki [1] . We've also begun
> implementing some of these ideas in a feature branch (which is work in
>
> progress) [2].  We’d appreciate any questions or feedback you may have.
>
>
>
> Thanks,
>
>
>
> -yolanda
>
>
>
> [1] -
>
>
> https://cwiki.apache.org/confluence/display/NIFI/Operational+Analytics+Framework+for+NiFi
>
> [2] - https://github.com/apache/nifi/commits/analytics-framework
>
>
>
> On Wed, Jul 31, 2019 at 9:58 AM Andy Christianson  .invalid> wrote:
>
>
>
> > As someone who operated a 24/7 mission-critical NiFi flow, this
>
> > feature would have been a life saver. If I'm heading home on a Friday,
>
> > it would be great to have some blinking red lights to let me know that
>
> > the system predicts that it is going to experience backpressure
>
> > sometime over the weekend, so that corrective action could be taken
> before leaving.
>
> >
>
> > Since there is support in the community for this, I created a JIRA to
>
> > track the effort:
>
> >
>
> > https://issues.apache.org/jira/browse/NIFI-6510
>
> >
>
> > I also created a JIRA to track the remote protocol:
>
> >
>
> > https://issues.apache.org/jira/browse/NIFI-6511
>
> >
>
> >
>
> > Regards,
>
> >
>
> > Andy
>
> >
>
> >
>
> > Sent from ProtonMail, Swiss-based encrypted email.
>
> >
>
> > ‐‐‐ Original Message ‐‐‐
>
> > On Wednesday, July 31, 2019 6:57 AM, Arpad Boda  > wrote:
>
> >
>
> > > If you could share a bit more details about your OPC and Modbus
>
> > > usage,
>
> > that
>
> > > would be highly appreciated!
>
> > >
>
> > > On Wed, 

Re: [VOTE] Release Apache NiFi Flow Design System 0.2.0 (RC2)

[Robert Fellows]

* Verified the signature
* Verified the hashes
* Verified the build
* Verified README
* Verified the demo app works as expected
* Successfully npm link'd @nifi-fds/core in nifi-registry, worked with
documented updates.

+ 1 (non-binding)


-- Rob Fellows

On Tue, Jul 23, 2019 at 4:07 PM Scott Aslan  wrote:

> Hello,
>
>
> I am pleased to be calling this vote for the source release of Apache
>
> NiFi Flow Design System 0.2.0.
>
>
> The source zip, including signatures, etc. can be found at:
>
> https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.2.0/
>
>
> The Git tag is NIFI-FDS-0.2.0-RC2
>
> The Git commit ID is 0b2443fce830a69f45c2d096872f84871e814d17
>
>
> https://git-wip-us.apache.org/repos/asf?p=nifi-fds.git;a=commit;h=0b2443fce830a69f45c2d096872f84871e814d17
>
>
> Checksums of nifi-fds-0.2.0-source-release.zip:
>
> SHA1: d11a7bbd4bcb1a9fc09f69d0a87ba3c26c20318d
>
> SHA256: 6dd0d9f9e09e57c85ea435e282118b1289fe7ebbeb6cd987aeeafc895815431f
>
> SHA512:
>
> 34110b6f06c2bd21696a83f69f7d0d6840b669408e4c12cf0a6101b6596e977fa4dfb4b62ade5104f4ad7df369a278535e4bb6b65fb89dd793140d748f70c0d1
>
>
> Release artifacts are signed with the following key:
>
> https://people.apache.org/keys/committer/scottyaslan.asc
>
>
> KEYS file available here:
>
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
>
> 36 issues were closed/resolved for this release:
>
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12343453=12316020
>
>
> Release note highlights can be found here:
>
>
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiFlowDesignSystem0.2.0
>
>
> The vote will be open for 72 hours.
>
>
> Please download the release candidate and evaluate the necessary items
>
> including checking hashes, signatures, build from source, and test.
>
>
> The please vote:
>
>
> [ ] +1 Release this package as nifi-fds-0.2.0
>
> [ ] +0 no opinion
>
> [ ] -1 Do not release this package because...
>


-- 
---
Rob Fellows

Re: [VOTE] Release Apache NiFi Flow Design System 0.2.0

[Robert Fellows]

* Verified the signature
* Verified the hashes
* Build was successful
* Demo app works as expected

I also npm link'd the new @nifi-fds/core in NiFi-Registry to verify it will
work.
However, it wasn't clear in the README that it requires upgrading
dependencies in the consuming app (angular, rxjs, angular-material, ...).
Once those changes were made, it worked. I think it worth documenting that
in the README and/or the Wiki. I created a JIRA for it
https://issues.apache.org/jira/browse/NIFI-6474.

With that caveat:
+1 (non-binding) Release this package as nifi-fds-0.2.0

-- Rob


On Mon, Jul 22, 2019 at 7:19 PM Scott Aslan  wrote:

> Hello,
>
>
> I am pleased to be calling this vote for the source release of Apache
>
> NiFi Flow Design System 0.2.0.
>
>
> The source zip, including signatures, etc. can be found at:
>
> https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.2.0/
>
>
> The Git tag is NIFI-FDS-0.2.0-RC1
>
> The Git commit ID is cee69170d68db602b8acac0959ee9e91c1000599
>
>
> https://git-wip-us.apache.org/repos/asf?p=nifi-fds.git;a=commit;h=cee69170d68db602b8acac0959ee9e91c1000599
>
>
> Checksums of nifi-fds-0.2.0-source-release.zip:
>
> SHA1: 14e8f3e908ec0ddd3556ee52524c2a5a099b4370
>
> SHA256: ae92eebf2d0b818b44203c896cde95e8c0dbf9007f9d3909e0253b156cf4b102
>
> SHA512:
>
> 86940d676ff63b7f23762dc4c3fc48ed19e1e67e97f4606cebce31b7f6b0976c60da487f6d23ce9476a293fb8fb790bfbaa3a8f1cfee5c8797658ac00718c3d9
>
>
> Release artifacts are signed with the following key:
>
> https://people.apache.org/keys/committer/scottyaslan.asc
>
>
> KEYS file available here:
>
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
>
> 36 issues were closed/resolved for this release:
>
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12343453=12316020
>
>
> Release note highlights can be found here:
>
>
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiFlowDesignSystem0.2.0
>
>
> The vote will be open for 72 hours.
>
>
> Please download the release candidate and evaluate the necessary items
>
> including checking hashes, signatures, build from source, and test.
>
>
> The please vote:
>
>
> [ ] +1 Release this package as nifi-fds-0.2.0
>
> [ ] +0 no opinion
>
> [ ] -1 Do not release this package because...
>


-- 
---
Rob Fellows

Re: Re: UI Bug driving me crazy (NIFI-6455)

[Robert Fellows]

The issue is coming from a library used called slickgrid. Updating the
version to a newer version fixes the issue. Here is a PR with the fix:
https://github.com/apache/nifi/pull/3591

Thanks,
Rob

On Thu, Jul 18, 2019 at 4:16 PM Robert Fellows 
wrote:

> It appears to be related to the version of slickgrid used. I initially
> thought it might have something to do with the browser zoom level as well,
> but that turned out to not be the case. I'm close to having a solution.
>
> On Thu, Jul 18, 2019 at 3:52 PM Nanduri, Kalyan 
> wrote:
>
>> I am not sure if I am to soon to answer, I faced a similar issue with a
>> different processor and I found that my 'zoom' browser was at 75% and when
>> I changed it to 67% or 100% I could scroll to it.
>> Do you want to try something like that it might fix it?
>>
>>
>>
>> -Original Message-
>> From: Robert Fellows [mailto:rob.fell...@gmail.com]
>> Sent: Thursday, July 18, 2019 3:45 PM
>> To: dev@nifi.apache.org
>> Subject: [EXTERNAL] Re: UI Bug driving me crazy (NIFI-6455)
>>
>> I'll look into it.
>>
>> On Thu, Jul 18, 2019 at 2:43 PM Peter Wicks (pwicks) 
>> wrote:
>>
>> > I ran across a UI bug, but haven’t been able to figure it out on my
>> > own so I wrote up a ticket, NIFI-6455. The bug causes the last item on
>> > a scrollable Configure window to not be accessible. The scrollbar is
>> > the right size, but the last property is inaccessible. Showed up in
>> > 1.10 for both Configure Processor and Configure Controller Service
>> > windows, no issues with the same processor/controller service in 1.9.2.
>> >
>> > If you have a processor like GetSolr, which has a lot of property
>> > options, you can’t access the last one off the edge of the screen. I’m
>> > running into this on a custom processor also, and the last property is
>> > the most important one… Does not appear to be an issue with some other
>> > windows like NiFi History.
>> >
>> > I tried tracking it down, but I wasn’t able to quickly track down the
>> > root cause, so I’m looking for a little UI assistance from the team,
>> > and hopefully someone can quickly replicate it and confirm it’s not
>> > just my environment .
>> >
>> > Thanks,
>> >   Peter
>> >
>>
>>
>> --
>> ---
>> Rob Fellows
>>
>
>
> --
> ---
> Rob Fellows
>


-- 
---
Rob Fellows

Re: UI Bug driving me crazy (NIFI-6455)

[Robert Fellows]

I'll look into it.

On Thu, Jul 18, 2019 at 2:43 PM Peter Wicks (pwicks) 
wrote:

> I ran across a UI bug, but haven’t been able to figure it out on my own so
> I wrote up a ticket, NIFI-6455. The bug causes the last item on a
> scrollable Configure window to not be accessible. The scrollbar is the
> right size, but the last property is inaccessible. Showed up in 1.10 for
> both Configure Processor and Configure Controller Service windows, no
> issues with the same processor/controller service in 1.9.2.
>
> If you have a processor like GetSolr, which has a lot of property options,
> you can’t access the last one off the edge of the screen. I’m running into
> this on a custom processor also, and the last property is the most
> important one… Does not appear to be an issue with some other windows like
> NiFi History.
>
> I tried tracking it down, but I wasn’t able to quickly track down the root
> cause, so I’m looking for a little UI assistance from the team, and
> hopefully someone can quickly replicate it and confirm it’s not just my
> environment .
>
> Thanks,
>   Peter
>


-- 
---
Rob Fellows

Re: [VOTE] Release Apache NiFi Registry 0.4.0

[Robert Fellows]

+1 (non-binding) Release this package as nifi-registry-0.4.0

Ran through the release helper guide...
* Built with a clean local maven repository
* Ran the binary, everything running well.
* Ran TestRestAPI.java to exercise the API.
* UI testing, no issues found.


On Thu, May 16, 2019 at 5:36 PM Bryan Bende  wrote:

> Hello,
>
> I am pleased to be calling this vote for the source release of Apache
> NiFi Registry nifi-registry-0.4.0.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1145
>
> The Git tag is nifi-registry-0.4.0-RC1
> The Git commit ID is 4d7add09cd915b20dcc9959b49ecdf202d5eac2a
>
> https://gitbox.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=4d7add09cd915b20dcc9959b49ecdf202d5eac2a
>
> Checksums of nifi-registry-0.4.0-source-release.zip:
> SHA256: a8753372fbc24f7d293df6205c465edee7a4167d835811e84e27df3e609d2be1
> SHA512:
> 70ade1ba2dcf5363b6568669080a3607e5dfd3dffd28651ba5f6961db835e0f61ff7f9758757358800774e4e1063cdcfdd5d44a712a845e34052544cfce9b047
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/bbende.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 37 issues were closed/resolved for this release:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320920=12344183
>
> Release note highlights can be found here:
>
> https://cwiki.apache.org/confluence/display/NIFIREG/Release+Notes#ReleaseNotes-NiFiRegistry0.4.0
>
> The vote will be open for 96 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-registry-0.4.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>


-- 
---
Rob Fellows