Re: [VOTE] Release Apache NiFi NAR Maven Plugin 2.1.0 (RC1)

[Peter Turcsanyi]

+1 binding

Ran through the release verification guide.
Built nifi-nar-maven-plugin on Ubuntu 24.04, Java 21 (Zulu 21.0.4+7-LTS)
and Maven 3.9.9 with empty local repo.

Verified NIFI-13773: built nifi using the new version of the nar plugin and
nifi-api-2.0.0.

Thanks for RMing David!

Regards,
Peter Turcsanyi

On Mon, Sep 23, 2024 at 9:03 PM David Handermann <
exceptionfact...@apache.org> wrote:

> Team,
>
> I am pleased to be calling this vote for the source release of Apache
> NiFi NAR Maven Plugin 2.1.0.
>
> Please review the following guide for how to verify a release candidate
> build:
>
>
> https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification+for+NiFi+NAR+Maven+Plugin
>
> The source being voted on the and the convenience binaries are
> available on the Apache Distribution Repository:
>
> https://dist.apache.org/repos/dist/dev/nifi/nifi-nar-maven-plugin-2.1.0
>
> The build artifacts are available on the Apache Nexus Repository:
>
> https://repository.apache.org/content/repositories/orgapachenifi-1283/
>
> Git Tag: nifi-maven-2.1.0-RC1
> Git Commit ID: 33591a2b3cc2134218f6a56ed3fe4a5eb2e3fdad
> GitHub Commit Link:
>
> https://github.com/apache/nifi-maven/commit/33591a2b3cc2134218f6a56ed3fe4a5eb2e3fdad
>
> Checksums of nifi-nar-maven-plugin-2.1.0-source-release.zip
>
> SHA512:
> 098eeecc7e9217d5676320688c405eae26db502eb86098b2aafb7a02f5c9651da31558affec9804efbb387835d625d899a588b6f38ca059c1a82769b05e0e785
>
> 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: 1
>
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12355125
>
> Release note highlights can be found on the project wiki:
>
>
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiNARMavenPluginVersion2.1.0
>
> The vote will be open for 48 hours.
>
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test.
> Then please vote:
>
> [] +1 Release this package as nifi-nar-maven-plugin-2.1.0
> [] +0 no opinion
> [] -1 Do not release this package because...
>

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

[Peter Turcsanyi]

+1 binding

Went through the release verification guide.
Built nifi-api on Ubuntu 24.04, Java 21 (Zulu 21.0.4+7-LTS) and Maven 3.9.9
with empty local repo.

Also tried to build nifi against the new nifi-api artifact and found an
issue in the nifi nar maven plugin. Currently it cannot handle different
nifi-api and nifi-framework-api artifact versions.
Jira [1] has been created to improve the nar plugin.

Thanks for RMing David!

Regards,
Peter Turcsanyi

[1] https://issues.apache.org/jira/browse/NIFI-13773

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

[Peter Turcsanyi]

+1 (binding)

Verified signatures and hashes.

Built NiFi on Ubuntu 22.04 with Java 8 (Zulu 1.8.0_412-b08) and Java 11
(Zulu 11.0.23+9-LTS), Maven 3.9.8 with empty local repo.

Started up NiFi in secure / unsecure mode on Java 8 / 11.

Ran flows for validating:
 - NIFI-13181 Azure Blob and ADLS processors throw NoSuchMethodError when
Service Principal is used
 - NIFI-12231 Add completion strategy to FetchSmb

Thanks for RMing Pierre!

Regards,
Peter Turcsanyi

On Fri, Jul 5, 2024 at 10:00 PM Csaba Bejan  wrote:

> +1 (binding)
>
>- Went through the helper guide and did a clean build
>- Verified signatures and hashes
>- Built on OSX 14.2.1
>- Java version: 11.0.20, OpenJDK 64-Bit Server VM Zulu11.66+15-CA (build
>11.0.20+8-LTS, mixed mode)
>- Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546)
>- Started NiFi and created a simple flow
>- Started MiNiFi and verified integration with C2 Server. Played around
>with the C2 protocol (Operations - Update, Transfer, Describe...)
>
> Thanks for RMing, Pierre!
>
> Regards,
>
> Csaba
>
> On Fri, Jul 5, 2024 at 2:30 PM Matt Burgess  wrote:
>
> > +1 (binding) ran through the release helper and tested various flows
> > including NIFI-13422.
> >
> > Apache Maven 3.9.8 (36645f6c9b5079805ea5009217e36f2cffd34256)
> > Java version: 1.8.0_372, vendor: Azul Systems, Inc., runtime:
> >
> >
> /Users/mburgess/.sdkman/candidates/java/8.0.372-zulu/zulu-8.jdk/Contents/Home/jre
> > Default locale: en_US, platform encoding: UTF-8
> > OS name: "mac os x", version: "14.5", arch: "aarch64", family: "mac"
> >
> > Thanks for RM'ing Pierre!
> >
> > On Wed, Jul 3, 2024 at 9:01 AM Pierre Villard <
> pierre.villard...@gmail.com
> > >
> > wrote:
> >
> > > Team,
> > >
> > > I am pleased to be calling this vote for the source release of Apache
> > NiFi
> > > 1.27.0.
> > >
> > > Please review the following guide for how to verify a release candidate
> > > build:
> > >
> > >
> > >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification
> > >
> > > The source being voted on the and the convenience binaries are
> available
> > on
> > > the Apache Distribution Repository:
> > >
> > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.27.0
> > >
> > > The build artifacts are available on the Apache Nexus Repository:
> > >
> > > https://repository.apache.org/content/repositories/orgapachenifi-1276
> > >
> > > Git Tag: nifi-1.27.0-RC2
> > > Git Commit ID: e0c4461d90bd4f6e5f2b81765bcff5cd97ed3e18
> > > GitHub Commit Link:
> > >
> > >
> >
> https://github.com/apache/nifi/commit/e0c4461d90bd4f6e5f2b81765bcff5cd97ed3e18
> > >
> > > Checksums of nifi-1.27.0-source-release.zip
> > >
> > > SHA256:
> 0ac01d54eeceb4a4f4863880bf67dfa71e6a585036c5caf0546c592bf55ced48
> > > SHA512:
> > >
> > >
> >
> 675c7750752bf3092061c9eaac39a975955e9bf881e6bee3124c5842738d8c8626b6a551f33ef7a678018bd83e0323c1f0f0d79101255494d8ca91be7fc750f5
> > >
> > > Release artifacts are signed with the following key:
> > >
> > > https://people.apache.org/keys/committer/pvillard.asc
> > >
> > > KEYS file is available on the Apache Distribution Repository:
> > >
> > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > >
> > > Issues resolved for this version: 37
> > >
> > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12354832
> > >
> > > Release note highlights can be found on the project wiki:
> > >
> > >
> > >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.27.0
> > >
> > > The vote will be open for 72 hours.
> > >
> > > Please download the release candidate and evaluate the necessary items
> > > including checking hashes, signatures, build from source, and test.
> Then
> > > please vote:
> > >
> > > [] +1 Release this package as nifi-1.27.0
> > > [] +0 no opinion
> > > [] -1 Do not release this package because...
> > >
> >
>

Re: [VOTE] Release Apache NiFi 1.26.0 (RC1)

[Peter Turcsanyi]

+1 (binding)

Verified signatures and hashes.
Built NiFi on Ubuntu 22.04 with Java 8 (Temurin 1.8.0_412+8) and Java 11
(Temurin 11.0.23+9), Maven 3.9.6 with empty local repo.

Ran flows for validating:
 - NIFI-12837 Add DFS setting to smb processors
 - NIFI-12732 ListS3 should reset its tracking state after configuration
change
 - NIFI-12936 ListGCSBucket should reset its tracking state after
configuration change
 - NIFI-12928 Add Simple Write strategy in PutAzureDataLakeStorage

Thanks for RMing Pierre!

Regards,
Peter Turcsanyi

On Mon, May 6, 2024 at 4:09 PM Chris Sampson
 wrote:

> +1 (binding)
>
> Ran through the release helper. Verified signatures and hashes.
>
> Full clean build of RC with Java openjdk 11.0.23 2024-04-16 on macOS
> Sonoma 14.4.1 using the Maven Wrapper 3.9.6.
>
> Ran a selection of processors/flows, primarily focussed on Elasticsearch
> integration and HTTP Request/Response.
>
>
> Cheers,
>
> ---
> Chris Sampson
> IT Consultant
> chris.samp...@naimuri.com
>
>
> > On 6 May 2024, at 14:31, David Handermann 
> wrote:
> >
> > +1 binding
> >
> > - Verified signatures and hashes
> > - Ran build using Maven Wrapper 3.9.6
> > - Ran build on Ubuntu 22.04 with Azul Zulu JDK 1.8.0-382 x86_64
> >
> > Thanks Pierre!
> >
> > Regards,
> > David Handermann
> >
> > On Fri, May 3, 2024 at 7:47 AM Pierre Villard
> >  wrote:
> >>
> >> Team,
> >>
> >> I am pleased to be calling this vote for the source release of Apache
> NiFi
> >> 1.26.0.
> >>
> >> Please review the following guide for how to verify a release candidate
> >> build:
> >>
> >>
> https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification
> >>
> >> The source being voted on the and the convenience binaries are
> available on
> >> the Apache Distribution Repository:
> >>
> >> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.26.0
> >>
> >> The build artifacts are available on the Apache Nexus Repository:
> >>
> >> https://repository.apache.org/content/repositories/orgapachenifi-1265
> >>
> >> Git Tag: nifi-1.26.0-RC1
> >> Git Commit ID: 338083f6850b61cd2651e41bbd73b3cb5330d98c
> >> GitHub Commit Link:
> >>
> https://github.com/apache/nifi/commit/338083f6850b61cd2651e41bbd73b3cb5330d98c
> >>
> >> Checksums of nifi-1.26.0-source-release.zip
> >>
> >> SHA256: 75ea201c12bb99672b1f075c9520b5f7df8b24e033ec47121848b351a0d47790
> >> SHA512:
> >>
> 5b754d899ce8cff900d5871d44c2fda9224e69fe8a0fe9a7121f3359ed8881300e4d4d0b2fe5befea276e0495c7ebbed04cc307c18527aa7a1cea25a923a
> >>
> >> Release artifacts are signed with the following key:
> >>
> >> https://people.apache.org/keys/committer/pvillard.asc
> >>
> >> KEYS file is available on the Apache Distribution Repository:
> >>
> >> https://dist.apache.org/repos/dist/release/nifi/KEYS
> >>
> >> Issues resolved for this version: 128
> >>
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12354185
> >>
> >> Release note highlights can be found on the project wiki:
> >>
> >>
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.26.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.26.0
> >> [] +0 no opinion
> >> [] -1 Do not release this package because...
>
>

Re: additional credential needed in S3 connection

[Peter Turcsanyi]

Hi Glenda,

Based on the AWS documentation, AWS_CA_BUNDLE is not a client credential
but it references the SSL certificate of the AWS service.
*AWS_CA_BUNDLE: Specifies the path to a certificate bundle to use for HTTPS
certificate validation.*

If I understand your use case correctly, you are trying to connect to your
"internal" bucket which is hosted by a custom S3 compatible service. Not
the public AWS service with the public certificate. That's why you need to
specify a custom certificate for AWS CLI via the AWS_CA_BUNDLE environment
variable.
If this is the case, you can configure it using the SSL Context Service
property of PutS3Object. You will need to create a keystore with the
certificate first, and set it in the Truststore* properties of SSL Context
Service.

Regards,
Peter Turcsanyi

On Tue, Feb 13, 2024 at 9:57 PM Glenda Ramos  wrote:

> Hi,
>
>
>
> We are currently testing Apache NiFi 1.23.0 specifically the "PutS3Object"
> processor to automatically transfer data from remote site to an "internal"
> S3 bucket. The standard AWSCLI commands work and able to connect the bucket
> because we are able to pass in additional credentials like the
> AWS_CA_BUNDLE environment variable. That being said, we need AWS_CA_BUNDLE
> property added in order to connect successfully to our S3 bucket using
> Apache NiFi's "PutS3Object". I have tried passing this as a Parameter and
> made it available to the flow but it's not being used by the "PutS3Object"
> processor to connect. Is there a way we can add an additional property for
> the AWS credentials/config file? It looks like it's only looking for
> "accessKey" and "secretKey".
>
>
>
> Any help would be greatly appreciated.
>
>
>
> Respectfully,
>
> Glenda Ramos
>
> Application Engineer
>

Re: [VOTE] Release Apache NiFi 1.24.0 (RC5)

[Peter Turcsanyi]

+1 (binding)

Verified signatures and hashes.
Built NiFi on Ubuntu 20.04 with Java 8 (Adoptium 1.8.0_392-b08), Java 11
(Adoptium 11.0.21+9) and Java 17 (Adoptium 17.0.9+9), Maven 3.9.5 with
empty local repo.

Ran flows for validating:
 - NIFI-12151 StandardPrivateKeyService fails due to missing
BouncyCastleProvider
 - NIFI-12364 Upgrade snowflake-ingest-sdk to 2.0.4 and snowflake-jdbc to
3.14.3
 - NIFI-12271 PuAzureBlobStorage with FileResourceService - FileNotFound
should not rollback
 - NIFI-11987 PutAzureBlobStorage_v12 using FileResourceService may fail
with OutOfMemoryError
 - NIFI-11926 Add proxy handling in Azure Storage Credentials Services
 - NIFI-6240 Proxy Support for AzureEventHub processor via Websockets
 - NIFI-11918 ListenGRPC with SSL fails on Java 17
 - NIFI-12373 Add License and Notice to nifi-standard-shared-nar

Found an issue with NIFI-6240 (Proxy Support for AzureEventHub processor
via Websockets) but it is not a deal breaker. Filed NIFI-12412
(ConsumeAzureEventHub should support Blob checkpoint store access via
proxy) for fixing it.

Thanks for RMing Pierre!

Regards,
Peter Turcsanyi

On Sun, Nov 26, 2023 at 7:51 AM Eric Secules  wrote:

> +1 (non-binding)
>
> Built on linux Mint:
> Apache Maven 3.6.3
> Maven home: /usr/share/maven
> Java version: 17.0.8.1, vendor: Private Build, runtime:
> /usr/lib/jvm/java-17-openjdk-amd64
> Default locale: en_CA, platform encoding: UTF-8
> OS name: "linux", version: "5.15.0-89-generic", arch: "amd64", family:
> "unix"
>
> - verified signatures and hashes
> - verified git commit
> - built sources with contrib-check
> - ran nifi and ran a couple sample flows
>
> Thanks Pierre!
>
> -Eric
>
> On Sat, Nov 25, 2023 at 1:38 PM Márk Báthori 
> wrote:
>
> > +1 (non-binding)
> >
> > Built on:
> > - OSX 13.4
> > - Java version: Azul Zulu version 11.0.18
> > - Apache Maven 3.8.6
> >
> > - Went through the helper guide and did a full clean build with contrib
> > check
> > - Verified signatures and hashes
> >
> > Tested various simple flows successfully.
> >
> > Verified the following tickets:
> > - [NIFI-11177] - PutIceberg cannot write null Timestamp into Iceberg
> table
> > - [NIFI-12130] - PutIceberg: Ability to configure snapshot properties via
> > dynamic attributes
> > - [NIFI-11739] - Add ability to ignore missing fields in PutIceberg
> > - [NIFI-12054] - PutIceberg should produce a provenance send event
> >
> > Thank you for RMing Pierre!
> >
> > Regards,
> > Mark
> >
> > David Handermann  ezt írta (időpont: 2023.
> > nov. 25., Szo, 18:32):
> >
> > > +1 binding
> > >
> > > - Verified signatures and hashes
> > > - Ran build using Maven Wrapper 3.9.5
> > > - Ran build on macOS 14.1.1 with Azul Zulu JDK 1.8.0-392 AArch64
> > > - Ran build on macOS 14.1.1 with Azul Zulu JDK 17.0.9 AArch64
> > > - Ran build on Ubuntu 22.04 with Azul Zulu JDK 17.0.9 x86_64
> > >
> > > - Ran NiFi on macOS 14.1.1 with Azul Zulu JDK 17.0.9 AArch64
> > > - Verified NiFi OpenID Connect integration with Okta
> > >
> > > - NIFI-1874 Verified IdentityMimeType character set detection
> > > - NIFI-11303 Verified go to component link from Provenance view
> > > - NIFI-11874 Verified updated layout of Process Group settings
> > > - NIFI-12033 Verified EncryptContentAge and DecryptContentAge
> Processors
> > > - NIFI-12093 Verified EncryptContent Processor marked as deprecated
> > > - NIFI-12115 Verified ListenOTLP receiving Logs and Traces over HTTP/2
> as
> > > JSON
> > > - NIFI-12153 Verified Max String Length configurable in JSON Tree
> Reader
> > > - NIFI-12219 Verified Flow Configuration History search and filter
> > > - NIFI-12239 Verified system information printed to nifi-bootstrap.log
> > > - NIFI-12287 Verified Sources and Java Documentation JAR binaries
> > > skipped for NAR packages
> > > - NIFI-12311 Verified Custom Class Transform not supported for Jolt
> > > Advanced interface
> > > - NIFI-12373 Verified LICENSE and NOTICE included in
> > > nifi-standard-shared-nar
> > > - NIFI-12377 Verified Jython Script Engine marked as deprecated
> > > - NIFI-12392 Verified Additional Details linked in component
> > documentation
> > >
> > > Thanks Pierre!
> > >
> > > Regards,
> > > David Handermann
> > >
> > > On Thu, Nov 23, 2023 at 9:15 AM Pierre Villard
> > >  wrote:
> > > >
> > > > Team,
> > > >
> > > > I 

Re: ASN.1 to text file

[Peter Turcsanyi]

Hi Katarzyna,

You can use ConvertRecord with JASN1Reader on the reader side and Json, XML
or other record writers on the writer side. You will also need a source
processor to get the ASN.1 file from your external source (it depends on
the source you use).

The NAR bundle containing JASN1Reader is not part of the standard NiFi
distribution due to size limitations but it is released in the same process.
You need to download it and install it in your NiFi environment (copying to
'lib' or 'extensions' folders).

NAR module name: nifi-asn1-nar
Download link from Maven Central:
https://search.maven.org/remotecontent?filepath=org/apache/nifi/nifi-asn1-nar/1.23.2/nifi-asn1-nar-1.23.2.nar

Regards,
Peter Turcsanyi

On Wed, Sep 20, 2023 at 4:46 PM Katarzyna Janeczko (Nokia) <
katarzyna.janec...@nokia.com> wrote:

> Hi,
> I am writing to you to ask if it is possible to build a processor using
> already existing tools in Apache Nifi to convert ASN.1 file to
> text/json/yaml/csv file?
>
> Best,
> Katarzyna Janeczko
>

Re: [VOTE] Release Apache NiFi 1.23.1 (RC1)

[Peter Turcsanyi]

+1 (binding)

Verified signatures and hashes.
Built NiFi on Ubuntu 20.04 with Java 8 (Adoptium 1.8.0_382-b05), Java 11
(Adoptium 11.0.20+8) and Java 17 (Adoptium 17.0.8+7), Maven 3.9.4 with
empty local repo.

Ran flows for validating:
 - NIFI-11823: PutBigQuery cannot handle BigDecimal / NUMERIC
 - NIFI-11902: ListHDFS closes FileSystem in OnTrigger
 - NIFI-11918: ListenGRPC with SSL fails on Java 17
 - NIFI-11926: Add proxy handling in Azure Storage Credentials Services

Thanks for RMing David!

Regards,
Peter Turcsanyi

On Wed, Aug 16, 2023 at 7:40 PM Matt Burgess  wrote:

> +1 (binding)
>
> Ran through release helper, verified NIFI-11922 [1] and stored flows
> in Registry.
>
> Apache Maven 3.9.1 (2e178502fcdbffc201671fb2537d0cb4b4cc58f8)
> Java version: 17.0.7, vendor: Oracle Corporation, runtime:
> /Users/mburgess/.sdkman/candidates/java/17.0.7-oracle
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "13.4.1", arch: "aarch64", family: "mac"
>
> Good work team, and thanks for RM'ing David!
>
> [1] https://issues.apache.org/jira/browse/NIFI-11922
>
> On Tue, Aug 15, 2023 at 2:08 PM David Handermann
>  wrote:
> >
> > Team,
> >
> > I am pleased to be calling this vote for the source release of Apache
> NiFi
> > 1.23.1.
> >
> > 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.1/
> >
> > The build artifacts are available on the Apache Nexus Repository:
> >
> > https://repository.apache.org/content/repositories/orgapachenifi-1234
> >
> > Git Tag: nifi-1.23.1-RC1
> > Git Commit ID: f739e9dd2d476b3c0df5a806ff1dffd24be52916
> > GitHub Commit Link:
> >
> https://github.com/apache/nifi/commit/f739e9dd2d476b3c0df5a806ff1dffd24be52916
> >
> > Checksums of nifi-1.23.1-source-release.zip:
> >
> > SHA256: 01f5f67a9f9703232f6fe260f6c1da73f3e3a0764b8e8464f915cfad168278e6
> > SHA512:
> >
> f8a010ad5a5dd1f71fe04e5d2bf1c6637d2d0a8a7c580a0ff4dbd76c12c2e5ab4ac43e1f5314f9fca85cebe1606bd5e7ae0a8b62f577ddc68696ebd0155d
> >
> > 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
> >
> > 51 issues were closed/resolved for this release:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12353541
> >
> > Release note highlights can be found here:
> >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.23.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.23.1
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
>

Re: [DISCUSS] Prepare Apache NiFi 1.23.1 Release?

[Peter Turcsanyi]

+1, thanks David!

On Mon, Aug 14, 2023 at 8:56 AM Krisztina Zsihovszki 
wrote:

> +1
>
> Thanks, David!
>
> Krisztina
>
> On Mon, Aug 14, 2023 at 12:04 AM Matt Burgess 
> wrote:
>
> > +1, thank you David!
> >
> > On Sat, Aug 12, 2023 at 10:26 AM David Handermann
> >  wrote:
> > >
> > > Team,
> > >
> > > Following the release of Apache NiFi 1.23.0, several important bugs
> have
> > > been resolved in a few Processors [1], and there have been a handful of
> > > incremental dependency upgrades [2]. Preparing an incremental patch
> > release
> > > would provide the opportunity to incorporate these bug fixes and pull
> in
> > a
> > > selected number of dependency upgrades.
> > >
> > > I am willing to handle the Release Manager responsibilities. If there
> is
> > a
> > > positive response to this approach, I can put together a selected list
> of
> > > issues next week.
> > >
> > > Regards,
> > > David Handermann
> > >
> > > [1]
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20NIFI%20AND%20issuetype%20%3D%20Bug%20AND%20fixVersion%20%3D%201.24.0
> > >
> > > [2]
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20NIFI%20AND%20fixVersion%20%3D%201.24.0
> >
>

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

[Peter Turcsanyi]

+1 (binding)

Verified signatures and hashes.
Built NiFi on Ubuntu 20.04 with Java 8 (Adoptium 1.8.0_382-b05), Java 11
(Adoptium 11.0.20+8) and Java 17 (Adoptium 17.0.8+7), Maven 3.9.3 with
empty local repo.

Ran flows for validating:
- NIFI-11758 Add local file upload option in PutAzure*Storage processors
- NIFI-11699 Fix dynamic properties in SnowflakeComputingConnectionPool
- NIFI-11708 Upgrade snowflake-ingest-sdk to 2.0.1 and snowflake-jdbc to
3.13.33

Thanks for RMing David!

Regards,
Peter Turcsanyi

On Thu, Jul 27, 2023 at 7:02 PM Nandor Soma Abonyi
 wrote:

> +1 (binding)
>
> Went through the release helper guide.
> Connected to NiFi registry, imported and committed some flows.
>
> Verified new features:
> - NIFI-11758 Add local file upload option in PutAzure*Storage processors
>
> Verified for regression:
> - Azure ADLS and Blob_v12 related flows
> - MQTT related flows
>
> Apache Maven 3.9.0 (9b58d2bad23a66be161c4664ef21ce219c2c8584)
> Maven home: /usr/share/maven
> Java version: 1.8.0_362, vendor: Temurin, runtime: /opt/java/openjdk/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "6.3.12-orbstack-00210-ga4f4fae8883e", arch:
> "aarch64", family: "unix"
>
> Thanks for RM'ing David!
>
> Regards,
> Soma
>
> > On 2023. Jul 25., at 23:32, 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&version=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...
>
>

Re: [ANNOUNCE] New nifi PMC Member Nandor Soma Abonyi

[Peter Turcsanyi]

Congrats, Soma!

On Tue, Jun 27, 2023 at 1:11 AM Joe Witt  wrote:

> On behalf of the Apache NiFI PMC, I am very pleased to announce that Nandor
> has accepted the PMC's invitation to join the Apache NiFi PMC. We greatly
> appreciate the PR reviews and code contributions and release management
> work of Nandor.
>
> Please join us in congratulating and welcoming Nandor to the Apache NiFi
> PMC.
>
> Congratulations Nandor!
>

Re: [VOTE] Release Apache NiFi NAR Maven Plugin 1.5.1

[Peter Turcsanyi]

+1 (binding)

Verified signatures and hashes.
Built NiFi NAR Maven Plugin and then NiFi using the new plugin on macOS
Ventura 13.2.1 and on Ubuntu 20.04 (Java: Adoptium Temurin 11.0.18+10,
Maven: 3.9.2, empty local repo).
Checked some NARs and ran NiFi. No issues found.

Thanks for RMing Soma!

Regards,
Peter Turcsanyi

On Thu, Jun 15, 2023 at 12:55 AM Nandor Soma Abonyi
 wrote:

> Hello Apache NiFi Community,
>
> I am pleased to be calling this vote for the source release of Apache NiFi
> NAR Maven Plugin 1.5.1.
>
> The source being voted upon, including signatures, digests, etc. can be
> found at:
> https://dist.apache.org/repos/dist/dev/nifi/nifi-nar-maven-plugin-1.5.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+NAR+Maven+Plugin+release+candidate
>
> The Git tag is nifi-nar-maven-plugin-1.5.1-rc1
> The Git commit ID is 39fc959426ea405df6360969b55ae2adad47e1aa
>
> https://gitbox.apache.org/repos/asf?p=nifi-maven.git;a=commit;h=39fc959426ea405df6360969b55ae2adad47e1aa
>
> Checksums of nifi-nar-maven-plugin-1.5.1-source-release.zip:
> SHA256: 0ddc4efbfe504f9ed6477b8c572f2c6e5ba0c953e2e5b063bdfbd1f934eda6bf
> SHA512:
> a7281c8a3769db37e3491f3a5e54533b5f26bdcad99f8adb1e5609f1de17309aefb3d49eb9231e75a814e42566525b9afe4a11bda2c4ab48e8bab5a298b72b24
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/nsabonyi.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 3 issues were closed/resolved for this release:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12353009
>
> Release note highlights can be found here:
>
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiNARMavenPluginVersion1.5.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-nar-maven-plugin-1.5.1
> [ ] +0 no opinion
> [ ] -1 Do not release this package because …
>
>

Re: [VOTE] Release Apache NiFi 1.22.0 (RC1)

[Peter Turcsanyi]

+1 (binding)

Verified signatures and hashes.
Built NiFi on Ubuntu 20.04 with Java 11 (Adoptium Temurin 11.0.19+7) and
Maven 3.9.2 using empty local repo.

Ran flows for validating:
- NIFI-11255 Add allowable value for “Use ‘s3.region’" attribute
- NIFI-11369 MergeContent unexpected behaviour
- NIFI-11493 Property descriptors which modifies classpaths are not
resolved with default values
- NIFI-11535 Change WebSocket FlowFile removal when supplying HTTP headers
- NIFI-11585 Add ADLSCredentialsControllerServiceLookup
- NIFI-11586 Add AzureStorageCredentialsControllerServiceLookup_v12
- NIFI-11593 UI - Dependent Properties with No Allowable Values
- NIFI-11615 Logging fixes in AMQP bundle
- NIFI-11628 SimpleProcessLogger substitutes the "Object[] + Throwable"
arguments incorrectly

Thanks for RMing Joe!

Regards,
Peter Turcsanyi

On Fri, Jun 9, 2023 at 9:17 PM Michael Moser  wrote:

> +1 (binding)
>
> Ran through helper and verified checksums and signature of source release,
> verified git commit.
> Built on CentOS Linux release 7.9.2009, Apache Maven 3.8.6, Java version:
> 1.8.0_372, vendor: Red Hat, Inc., runtime:
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.372.b07-1.el7_9.x86_64/
> Ran NiFi and NiFi Registry on Java 1.8.0_372 and 11.0.19 with no issues
> with some very simple flows.
>
> Thanks to the team for this release, and Joe for doing RM.
>
> -- Mike
>
>
> On Fri, Jun 9, 2023 at 5:10 AM Ferenc Kis  wrote:
>
> > +1 (non-binding)
> >
> > Went through the helper guide, full clean build with contrib check,
> > verified signatures and hashes
> >   Maven home: /Users/fkis/.sdkman/candidates/maven/current
> >   Java version: 11.0.18, vendor: Eclipse Adoptium, runtime:
> > /Users/fkis/.sdkman/candidates/java/11.0.18-tem
> >   Default locale: en_HU, platform encoding: UTF-8
> >   OS name: "mac os x", version: "13.2.1", arch: "aarch64", family: "mac"
> >
> > Generic validation:
> > - Started NiFi, created a simple flow with ListenHTTP
> > - Started Nifi Registry, set up integration with NiFi, and saved the
> > previous flow to NiFi Registry
> > - Started MiNiFi Java:
> >   * created a simple GenerateFlowFile -> InvokeHttp flow and pushed to
> > MiNiFi via C2 protocol
> >   * managed to push data from MiNiFi to NiFi
> >
> > Specific validation:
> > NIFI-11366: set up C2 integration via new parameters. MiNiFi was able to
> > connect to C2 server behind proxy and to fetch flow updates
> > NIFI-11476: resource consumption data is populated in heartbeat response
> > and looks correct
> >
> > Thanks Joe for RMing!
> >
> > Regards
> > Ferenc
> >
> > On Fri, Jun 9, 2023 at 3:54 AM Andrew Lim 
> > wrote:
> >
> > > +1 (binding)
> > >
> > > -Ran full clean install on OS (Ventura 13.0.1, OpenJDK version
> 1.8.0_372)
> > > -Tested secure NiFi with secure NiFi Registry
> > > -Ran basic flows successfully; tested basic versioned flow
> functionality
> > >
> > > Drew
> > >
> > > > On Jun 6, 2023, at 5:38 PM, Joe Witt  wrote:
> > > >
> > > > Hello,
> > > >
> > > > I am pleased to be calling this vote for the source release of Apache
> > > NiFi
> > > > 1.22.0.
> > > >
> > > > The source zip, including signatures, digests, etc. can be found at:
> > > >
> https://repository.apache.org/content/repositories/orgapachenifi-1228
> > > >
> > > > The source being voted upon and the convenience binaries can be found
> > at:
> > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.22.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.22.0-RC1
> > > > The Git commit ID is 71e3ea9f2c58d0cf2ce6824c388f2bd3e917dfc8
> > > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=71e3ea9f2c58d0cf2ce6824c388f2bd3e917dfc8
> > > >
> > >
> >
> https://github.com/apache/nifi/commit/71e3ea9f2c58d0cf2ce6824c388f2bd3e917dfc8
> > > >
> > > > Checksums of nifi-1.22.0-source-release.zip:
> > > > SHA256:
> > d63a5f1db95160434670f112a0ee6e06fa141182bd0f12f0e58e3229991f3743
> > > > SHA512:
> > > >
> > >
> >
> 5f6da64e75a2d5446f1f274fe3de7e97290f5b916eabbc0491

Re: [VOTE] Release Apache NiFi 1.20.0 (RC1)

[Peter Turcsanyi]

+1 (binding)

- Verified signatures and hashes.
- Built NiFi on Ubuntu 20.04 with Java 8 (Adoptium Temurin
1.8.0_362-b09), Java 11 (Adoptium Temurin 11.0.18+10) and Java 17
(Adoptium Temurin 17.0.6+10).
- Ran flows for testing:
-- NIFI-10868 PutDropbox processor
-- NIFI-10965 PutGoogleDrive processor
-- NIFI-11059 PutBoxFile processor
-- NIFI-10846 SMB issue

Thanks for RMing Joe!

Regards,
Peter Turcsanyi

On Thu, Feb 9, 2023 at 8:30 PM Pierre Villard
 wrote:
>
> +1 (binding)
>
> - Went through the usual step for checking the source code, signature,
> hashes, etc
> - Built with Java 11
> - Deployed secured 3-nodes NiFi cluster with secured NiFi Registry on GCP
> and confirmed everything is working as expected on some common flows I have
>
> Thanks for taking care of this release Joe!
>
>
> Le jeu. 9 févr. 2023 à 20:26, Mark Payne  a écrit :
>
> > +1 (binding)
> >
> > - Performed full build with contrib-check. I did run into a unit test
> > failure in standard-processors, but running a second time was successful.
> > Seems to be some sort of intermittent failure with TestFTP. One FlowFile
> > was expected to go to ‘failure’, I believe and went to comms.failure
> > instead.
> > - Ran through all system tests successfully
> > - Verified hashes
> > - Verified signature
> > - Ran a simple flow to ensure normal operations worked as expected.
> >
> > Thanks
> > -Mark
> >
> >
> > > On Feb 6, 2023, at 3:54 PM, Joe Witt  wrote:
> > >
> > > Hello,
> > >
> > > I am pleased to be calling this vote for the source release of Apache
> > NiFi
> > > 1.20.0.
> > >
> > > The source zip, including signatures, digests, etc. can be found at:
> > > https://repository.apache.org/content/repositories/orgapachenifi-1220
> > >
> > > The source being voted upon and the convenience binaries can be found at:
> > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.20.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.20.0-RC1
> > > The Git commit ID is 81296b5b69a69d26afb8f8dec3a58a8363653890
> > >
> > https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=81296b5b69a69d26afb8f8dec3a58a8363653890
> > >
> > > Checksums of nifi-1.20.0-source-release.zip:
> > > SHA256: 694e9eec951caf628576a2aaa16e7ddadc11b9bf455f16d503bdd88aefdbfe66
> > > SHA512:
> > >
> > f54891aadbf58eaf4df465e99eb935ddbb47c70c1e329968098762f670eeed56a427ed88f21f150c056f8b057f7120127f3470afe4f4f89b80d659d7b8080339
> > >
> > > 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
> > >
> > > 205 issues were closed/resolved for this release:
> > >
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12352581
> > >
> > > Release note highlights can be found here:
> > >
> > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.20.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.20.0
> > > [ ] +0 no opinion
> > > [ ] -1 Do not release this package because...
> >
> >

Re: [VOTE] Release Apache NiFi 1.19.0 (RC1)

[Peter Turcsanyi]

+1 (binding)

- Verified signatures and hashes.
- Built NiFi on Ubuntu 20.04 with Java 8 (Adoptium Temurin
1.8.0_352-b08), Java 11 (Adoptium Temurin 11.0.17+8) and Java 17
(Adoptium Temurin 17.0.5+8).
- Ran NiFi on the java versions above.
- Ran flows for testing:
-- new Snowflake processors (NIFI-10370)
-- new Iceberg processor (NIFI-10442)
-- MQTT failover (NIFI-10543)
-- other smaller changes (NIFI-10349, NIFI-10656, NIFI-10317)

Found some issues but these are not blockers. Jiras created:
- NIFI-10883: SnowflakeComputingConnectionPool fails on Java 17
- NIFI-10884: Conflict resolution in PutAzureDataLakeStorage should
log the target filename
- NIFI-10885: ConsumeMQTT should stop client threads

Thanks for RMing Joe!

Regards,
Peter Turcsanyi

On Mon, Nov 28, 2022 at 4:53 AM Mark Bean  wrote:
>
> +1 (non-binding)
>
> Verified checksums and signatures.
> Performed full build with -Pcontrib-check using OpenJDK 1.8.0_352, 11.0.17,
> 17.0.5
> Ran several relatively simple flows in non-cluster mode only. No issues
> observed.
>
> I don't believe this is worth holding up the 1.19.0 release, but while
> everything worked as expected with Java 8 and 11, there were some issues
> with Java 17 in generating documentation for several of the "scripted"
> processors, controller services and a reporting task. The following is from
> the nifi-app.log. And, in the UI, the documentation was not full/complete
> for these processors.
>
> 2022-11-27 20:50:27,703 WARN [main]
> o.apache.nifi.documentation.DocGenerator Documentation generation failed:
> Component Class [class
> org.apache.nifi.processors.script.InvokeScriptedProcessor]
> 2022-11-27 20:50:28,243 WARN [main]
> o.apache.nifi.documentation.DocGenerator Documentation generation failed:
> Component Class [class org.apache.nifi.processors.script.ExecuteScript]
> 2022-11-27 20:50:28,311 WARN [main]
> o.apache.nifi.documentation.DocGenerator Documentation generation failed:
> Component Class [class
> org.apache.nifi.record.sink.script.ScriptedRecordSink]
> 2022-11-27 20:50:28,313 WARN [main]
> o.apache.nifi.documentation.DocGenerator Documentation generation failed:
> Component Class [class
> org.apache.nifi.record.script.ScriptedRecordSetWriter]
> 2022-11-27 20:50:28,315 WARN [main]
> o.apache.nifi.documentation.DocGenerator Documentation generation failed:
> Component Class [class org.apache.nifi.lookup.script.ScriptedLookupService]
> 2022-11-27 20:50:28,323 WARN [main]
> o.apache.nifi.documentation.DocGenerator Documentation generation failed:
> Component Class [class
> org.apache.nifi.lookup.script.SimpleScriptedLookupService]
> 2022-11-27 20:50:28,326 WARN [main]
> o.apache.nifi.documentation.DocGenerator Documentation generation failed:
> Component Class [class
> org.apache.nifi.rules.handlers.script.ScriptedActionHandler]
> 2022-11-27 20:50:28,327 WARN [main]
> o.apache.nifi.documentation.DocGenerator Documentation generation failed:
> Component Class [class org.apache.nifi.record.script.ScriptedReader]
> 2022-11-27 20:50:28,328 WARN [main]
> o.apache.nifi.documentation.DocGenerator Documentation generation failed:
> Component Class [class
> org.apache.nifi.rules.engine.script.ScriptedRulesEngine]
> 2022-11-27 20:50:28,521 WARN [main]
> o.apache.nifi.documentation.DocGenerator Documentation generation failed:
> Component Class [class
> org.apache.nifi.reporting.script.ScriptedReportingTask]
>
> On Sun, Nov 27, 2022 at 4:35 PM Nandor Soma Abonyi
>  wrote:
>
> > +1 (non-binding)
> >
> > I’ve found two minor issues. I believe none of them is a blocker, but we
> > should follow up on them. Marked them with ***.
> >
> > Went through the release helper guide on:
> > Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
> > Java version: 1.8.0_332, vendor: Temurin
> > Default locale: en_US, platform encoding: UTF-8
> > OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac"
> >
> > Imported flows from NiFi registry for these issues and verified them:
> > - NIFI-10760 - Add Api key authentication option to
> > ElasticSearchClientServiceImpl
> > - *** A validation has been removed, which prevented using Basic and
> > Api Key properties together.
> >  If I set Username/Password and hide them by selecting Api Key
> > Authorization Scheme, the client will still use those credentials. If I set
> > Api Key, the client will add both credentials as a request header.
> >  Opened NIFI-10880 for further discussion.
> > - NIFI-10668 - Persist proxy password in remote process group
> > - NIFI-10656 - Log ignored event with info instead of warning in PutADLS
> > - NIFI-10650

Re: [VOTE] Release Apache NiFi 1.18.0 (RC4)

[Peter Turcsanyi]

+1 (binding)

- Verified signatures and hashes.
- Built NiFi on Ubuntu 20.04 with Java 8 (Adoptium Temurin
1.8.0_345-b01), Java 11 (Adoptium Temurin 11.0.16.1+1) and Java 17
(Adoptium Temurin 17.0.4.1+1).
- Ran some simple flows with newly added processors (GetHubSpot,
GetShopify, QueryAirtableTable and MQTT v5 support).

Found an issue with GetHubSpot / GetShopify [1] but it should not be a
release blocker because it is not a regression (as they are new
processors) and it is about data duplication, not data loss.

Thanks for RMing Joe!

Regards,
Peter

[1] - https://issues.apache.org/jira/browse/NIFI-10602

On Thu, Oct 6, 2022 at 9:57 PM Joe Witt  wrote:
>
> +1 binding
>
> On Thu, Oct 6, 2022 at 12:54 PM Mark Payne  wrote:
> >
> > +1 (binding)
> >
> > - Performed full build with contrib-check
> > - Started a simple instance and verified that I was able to create 
> > Parameter Context from AWS Secrets Manager
> > - Ran a simple GenerateFlowFile -> UpdateAttribute flow. Performance was 
> > roughly on-par with historical builds.
> >
> > Thanks for performing the RC again, Joe!
> >
> > -Mark
> >
> > > On Oct 3, 2022, at 4:44 PM, Joe Witt  wrote:
> > >
> > > Hello,
> > >
> > > I am pleased to be calling this vote for the source release of Apache
> > > NiFi 1.18.0.
> > >
> > > The source zip, including signatures, digests, etc. can be found at:
> > > https://repository.apache.org/content/repositories/orgapachenifi-1214
> > >
> > > The source being voted upon and the convenience binaries can be found at:
> > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.18.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.18.0-RC4
> > > The Git commit ID is 109e54cd585902a981d1b370b3dc4d1620be438c
> > > https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=109e54cd585902a981d1b370b3dc4d1620be438c
> > >
> > > Checksums of nifi-1.18.0-source-release.zip:
> > > SHA256: 925cbb92c107d0fa3194a349d985cff4933a61b2555eff57b1b81433fe37c139
> > > SHA512: 
> > > f143215b1746342e7584f5ad65b546fcc378cd78aa17628fb605dfdbbaf11e897a0173dd67807fc90cb18c17124a4227d5fe07e7ed609d9ed1904503b757c604
> > >
> > > 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
> > >
> > > 184 issues were closed/resolved for this release:
> > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12352150
> > >
> > > Release note highlights can be found here:
> > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.18.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.18.0
> > > [ ] +0 no opinion
> > > [ ] -1 Do not release this package because...
> >

Re: Jira contributor access

[Peter Turcsanyi]

Hi,

Granted Jira contributor access. Looking forward to your contributions.

Regards,
Peter Turcsanyi

On Wed, Sep 28, 2022 at 7:50 AM Lifeng Ai  wrote:
>
> Hi,
>
> Can I get "Jira contributor access"? My id is ailifeng. Thank you!
>
> Best regards,
> Tom Ai

Re: "Jira contributor access" needed

[Peter Turcsanyi]

Hi Akshara,

Granted Jira contributor access. Looking forward to your contributions.

Regards,
Peter Turcsanyi

On Wed, Sep 14, 2022 at 6:38 AM Akshara Uke  wrote:
>
> Hello,
>
> Please grant "Jira contributor access" to aksharau
>
>
> Thanks much,
>
> akshara

Re: First time contributor to NiFi

[Peter Turcsanyi]

Hi Saumya,

For becoming a contributor, you will need to ask for "Jira contributor
access" as described in the Contributor Guide [1].
Please send over your jira user name and we can grant access to assign
the tickets to yourself.

Regards,
Peter Turcsanyi

[1] https://cwiki.apache.org/confluence/display/NIFI/Contributor+Guide


On Tue, Sep 13, 2022 at 12:00 PM Saumya Gurtu  wrote:
>
> Hi all,
>
> I am a first time contributor to the NiFi repository. I have worked on two
> issues. Please review my PRs
>
> https://github.com/apache/nifi/pull/6382
> https://github.com/apache/nifi/pull/6383
>
> Thanks,
> Saumya Gurtu
> Sr. Software Engineer @ VISA Inc.

Re: request "Jira contributor access

[Peter Turcsanyi]

Dan,

Added you as a contributor to the NiFi Jira project. Looking forward
to your contributions.

On Fri, Aug 19, 2022 at 3:50 PM Dan S  wrote:

> Jira username dstiegli1
>

Re: recent Nifi version compabible with JDK 1.8

[Peter Turcsanyi]

Hi Prakash,

The latest released NiFi is 1.16.3 so I'm not sure what you mean by 1.19.2.

NiFi 1.16.3 is Java 8 compatible and contains the log4j vulnerability fixes
(from 1.15.3 on).

You can check it on the release notes page:
https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.15.3

Regards,
Peter Turcsanyi

On Tue, Jul 5, 2022 at 4:26 PM Prakash Venuthurupalli 
wrote:

> Hi,
>
>Which recent version of NiFi is compatible with JDK 1.8 ?
> We are using NiFi version 1.19.2. Is this version taking care of the log4j
> vulnerability?
> To fix log4j libraries, which NiFi version should we use? Is it compatible
> with JDK 1.8 ?
> Do we need to individually download lo4j libraries to patch NiFi 1.19.2 ?
>
> Thanks
> Prakash
>

Re: [VOTE] Release Apache NiFi 1.16.3 (RC1)

[Peter Turcsanyi]

+1 (binding)

- Verified signatures and hashes.
- Built NiFi on Ubuntu 20.04 with Java 8 (Adoptium Temurin 1.8.0_332-b09),
Java 11 (Adoptium Temurin 11.0.15+10) and Java 17 (Adoptium Temurin
17.0.3+7).
- Ran some simple flows.

Thanks for RMing Joe!

Peter

On Tue, Jun 14, 2022 at 10:18 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
>
> Drew
>
> > On Jun 14, 2022, at 12:38 AM, Joe Witt  wrote:
> >
> > Hello,
> >
> > I am pleased to be calling this vote for the source release of Apache
> NiFi
> > 1.16.3.
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > https://repository.apache.org/content/repositories/orgapachenifi-1205
> >
> > The source being voted upon and the convenience binaries can be found at:
> > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.16.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.16.3-RC1
> > The Git commit ID is e15bdd7e3d09047d5fed70117b7c3dfd26f3a36e
> >
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=e15bdd7e3d09047d5fed70117b7c3dfd26f3a36e
> >
> > Checksums of nifi-1.16.3-source-release.zip:
> > SHA256: c18edf739361246fe22bb4c2e5a4b1936b6199512b78638868f99b1d827b4d9e
> > SHA512:
> >
> e3c9942737a0c2cf43fb3030da3cbee7d6be17038f0cf683c9522db25eb6d8664884594d5a7ce2183733568c06b9ccb52c3a6bf6d5ddcb334d2f84477cc68177
> >
> > 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
> >
> > 13 issues were closed/resolved for this release:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12351844
> >
> > Release note highlights can be found here:
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.16.3
> >
> > The vote will be open for 24 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.3
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
>
>

Re: Nifi ListS3 issue

[Peter Turcsanyi]

Hi Natalia,

It seems you have an issue with your cluster / state management setup.
Please check your state-management.xml config.

Regards,
Peter Turcsanyi

On Tue, May 31, 2022 at 1:33 PM Fill, Natalia  wrote:

> Hi Apache Nifi team,
>
>
>
> I have a ListS3 processor that works perfectly well on DEV and QA Nifi
> cluster but fails in UAT with error: "A HostProvider may not be empty". The
> processor configuration is identical between environments.
>
> Interesting point is that it does PutS3 correctly in UAT, but fails to
> Lists3. The ListS3 was configured to run on primary node only.
>
> Do you have any suggestions what could be the cause for this error?
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Thank you
>
>
>
> Natalia Fill
> Analyst Software Developer
> Legal and General Investment Management, One Coleman Street, London, EC2R
> 5AA
>
> natalia.f...@lgim.com
>
>
> This e-mail (and any attachments) may contain privileged and/or
> confidential information which may be protected by copyright or other
> intellectual property rights. If you are not the intended recipient please
> do not disclose, copy, distribute, disseminate or take any action in
> reliance on it. If you have received this e-mail in error please reply to
> the sender and then immediately delete it (including, any attachments).
> Should you wish to communicate with us by e-mail we cannot guarantee the
> security of any data outside our own computer systems or that any e-mail
> will be virus free.
>
> Any information contained in this e-mail may be subject to applicable
> terms and conditions and must not be construed as giving investment advice
> within or outside the United Kingdom or the Republic of Ireland.
>
> Telephone conversations and calls via other telecommunication facilities
> may be recorded, including to comply with our legal and/or regulatory
> requirements and/or to monitor the quality of our service. For information
> about how we use your personal data, including your legal rights, please
> refer to our privacy policy at:
> www.legalandgeneral.com/institutional/privacy-policy/.
>
> Legal & General Investment Management Limited (Company number 02091894),
> LGIM Real Assets (Operator) Limited (Company number 05522016), LGIM
> International Limited (Company number 07716001), Legal & General (Unit
> Trust Managers) Limited (Company number 01009418), GO ETF Solutions LLP
> (Company number OC329482) and LGIM Corporate Director Limited (Company
> number 07105051) are each authorised and regulated by the Financial Conduct
> Authority. All are registered in England & Wales with a registered office
> at One Coleman Street, London, EC2R 5AA.
>
> Legal and General Assurance (Pensions Management) Limited (Company number
> 01006112) is authorised by the Prudential Regulation Authority and
> regulated by the Financial Conduct Authority and the Prudential Regulation
> Authority. It is registered in England & Wales with a registered office at
> One Coleman Street, London, EC2R 5AA.
>
> Legal & General Property Limited (Registration number 02091897) is
> authorised and regulated by the Financial Conduct Authority for insurance
> mediation activities. It is registered in England & Wales with a registered
> office at One Coleman Street, London, EC2R 5AA.
>
> LGIM Managers (Europe) Limited is authorised and regulated by the Central
> Bank of Ireland (Reference No C173733). It is registered in the Republic of
> Ireland (Number 609677) with its principal business address at 33/34 Sir
> John Rogerson's Quay, Dublin 2, D02 XK09.
>
> The ultimate parent company is Legal & General Group PLC (Company number
> 01417162) which is registered in England & Wales and has a registered
> office at One Coleman Street, London, EC2R 5AA.
> 
>  This email has come from the internet and has been scanned for all
> viruses and potentially offensive content by Messagelabs on behalf of Legal
> & General 
>

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

[Peter Turcsanyi]

+1 (binding)

- Verified signatures and hashes.
- Built NiFi on Ubuntu 20.04 with Java 8 (Adoptium Temurin 1.8.0_332-b09),
Java 11 (Adoptium Temurin 11.0.15+10) and Java 17 (Adoptium Temurin
17.0.3+7).
- Ran NiFi with different JRE versions (Java 8 binary on JRE 8, 11 and 17,
etc).
- Tested the following jiras with simple flows:
-- NIFI-9978: Verified "Download flow definition" menu
-- NIFI-9980: Verified GCP PubSub processors
-- NIFI-9991: Verified ASN1 RecordReader processes multiple records
-- NIFI-10003: Verified ExecuteScript with Python running in UTC+2 time zone

Regards,
Peter Turcsanyi


On Wed, May 25, 2022 at 6:14 PM Paul Grey  wrote:

> +1 (non-binding)
>
> - Verified signatures and hashes of [
> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.16.2/] binaries
> - Build of source successful (macOS 12 / Azul Java 1.8.0_322)
> - Application startup successful (set-single-user-credentials, five node
> dev cluster)
> - Verified successful flow of data using known good flows (Kafka, PutSlack)
> - Testing of cluster disconnect / offload / connect operations
> - JIRAs NIFI-10053, NIFI-10055 created for minor issues
>
> On Tue, May 24, 2022 at 7:09 PM Nathan Gough  wrote:
>
> > +1 (non-binding)
> >
> > Tested out 3 node secure cluster and external ZK with a few different
> > processors, set up and tested Google OIDC authentication.
> >
> > Nathan
> >
> > On Tue, May 24, 2022 at 5:54 PM Mark Payne  wrote:
> >
> > > +1 (binding)
> > >
> > > Performed build with Java 8.
> > > Ran with Java 8 and Java 11.
> > > Tested insecure standalone installation
> > > Tested secured (via certificate) clustered installation
> > >
> > > Did heavy testing against controller services, restarts, trying to
> > > introduce corner cases.
> > > Validated that NIFI-10001 was addressed.
> > >
> > > I did encounter a couple of bugs that I created Jiras for but none were
> > > critical and none were regressions introduced in this release.
> > >
> > > Thanks for handling the RM duties again Joe!
> > >
> > > -Mark
> > >
> > >
> > > > On May 22, 2022, at 11:44 PM, Joe Witt  wrote:
> > > >
> > > > Hello,
> > > >
> > > > I am pleased to be calling this vote for the source release of Apache
> > > NiFi
> > > > 1.16.2.
> > > >
> > > > The source zip, including signatures, digests, etc. can be found at:
> > > >
> https://repository.apache.org/content/repositories/orgapachenifi-1203
> > > >
> > > > The source being voted upon and the convenience binaries can be found
> > at:
> > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.16.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.16.2-RC3
> > > > The Git commit ID is 06f04958272dafc30ce357c4c4edcaf470050b52
> > > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=06f04958272dafc30ce357c4c4edcaf470050b52
> > > >
> > > > Checksums of nifi-1.16.2-source-release.zip:
> > > > SHA256:
> > 1fecf7d9f6001cc8e58d4a46ece08e141de705bcd227338ba79e9cb574267415
> > > > SHA512:
> > > >
> > >
> >
> 1f4fd4e5e9f24949830a75949b302a67b8826049406ab8296c4b8c99a5a0aa1d211f84f98699b3af6fb41efa305f35a3f85b21d7958dc09c027cc1ed836c169f
> > > >
> > > > 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
> > > >
> > > > 34 issues were closed/resolved for this release:
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12351721
> > > >
> > > > Release note highlights can be found here:
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.16.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.16.2
> > > > [ ] +0 no opinion
> > > > [ ] -1 Do not release this package because...
> > >
> > >
> >
>

Re: [EXTERNAL] Re: Nifi putting object to S3 directory

[Peter Turcsanyi]

Hi Natalia,

You can set the "directory" in the Prefix property of ListS3. In this case
no UpdateAttribute is needed, just connect ListS3 -> FetchS3Object.

Regards,
Peter Turcsanyi

On Mon, May 16, 2022 at 4:24 PM Fill, Natalia  wrote:

> Hi Nifi Team,
>
> Following from tests below I need to retrieve files from specific
> directories on S3. The files are placed into dir/subdir/.
> I tried various expression to specify 'filename' variable that feeds to
> FetchS3Object and still get error that the key doesn't exist.
> I am not sure if FetchS3Object doesn't like my directories pattern or the
> file name. If I don't specify any pattern and just fetch what was listed,
> it works fine.
> The flow goes as follows: ListS3 (lists all the files as expected) -
> UpdateAttribute (updates filename with the pattern to use) - FetchS3Object
> - LogAttribute on success and on failure.
>
> Some of my tries for filename pattern below:
> *( dir/subdir/test_put_\d*_\d*\.txt).*
> *( test_put_\d*_\d*\.txt).*
> dir/subdir /test_put_\d*_\d*\.txt
> dir/subdir /test_put_${now():format('-MM-dd')}_*
> /dir/subdir /test_put_${now():format('-MM-dd')}_*
>
> List of files on s3 server is like below:
> 2022-05-16 13:36:03 14 test_put_20220516_013601.txt
> 2022-05-16 13:36:04 14 test_put_20220516_013602.txt
>
> Can anyone suggest how do I retrieve files in dir/subdir that start with a
> particular string (e.g. test_put_) contain today's date and end with
> sequence of numbers.
>
> Thanks
> Natalia
>
> .
> -Original Message-
> From: Fill, Natalia
> Sent: 16 May 2022 13:15
> To: dev@nifi.apache.org
> Subject: RE: [EXTERNAL] Re: Nifi putting object to S3 directory
>
> Thanks Peter, removing leading slash worked and now Nifi puts file into
> specified subdirectory.
>
> This is a simple test flow to test read/write to s3: GenerateFlowFile - on
> success - UpdateAttribute (filename to meaningful name) - on success -
> PutS3Object - on success and on failure LogAttribute
>
> Regards
> Natalia
>
> -Original Message-
> From: Peter Turcsanyi 
> Sent: 16 May 2022 12:41
> To: dev@nifi.apache.org
> Subject: [EXTERNAL] Re: Nifi putting object to S3 directory
>
> CAUTION: This email originated from outside of the organisation. Do not
> click links or open attachments unless you recognise the sender and know
> the content is safe.
>
>
> Hi Natalia,
>
> Is the FlowFile transferred to the success or the failure relationship
> from PutS3Object?
>
> In general, you need to use dirtag/subdirtag /${filename}, so no leading
> slash.
> Leading slash results in a directory called '/' on S3.
>
> Regards,
> Peter Turcsanyi
>
> On Mon, May 16, 2022 at 12:46 PM Fill, Natalia 
> wrote:
>
> > Hi Nifi Team,
> >
> > I am working on a solution to put file into S3 server. I used
> > PutS3Object and managed to put some files into a bucket, but it failed
> > to put files into specific directories on S3. No errors, but I don't
> > see the files in the bucket. I used the following format for object key:
> > /dirtag/subdirtag /${filename}. The tags do exist on S3.
> >
> > Does anyone have any suggestions how to put S3 object into specific
> > directory and not just on top level in a bucket.
> >
> > Thanks
> > Natalia
> > This e-mail (and any attachments) may contain privileged and/or
> > confidential information which may be protected by copyright or other
> > intellectual property rights. If you are not the intended recipient
> > please do not disclose, copy, distribute, disseminate or take any
> > action in reliance on it. If you have received this e-mail in error
> > please reply to the sender and then immediately delete it (including,
> any attachments).
> > Should you wish to communicate with us by e-mail we cannot guarantee
> > the security of any data outside our own computer systems or that any
> > e-mail will be virus free.
> >
> > Any information contained in this e-mail may be subject to applicable
> > terms and conditions and must not be construed as giving investment
> > advice within or outside the United Kingdom or the Republic of Ireland.
> >
> > Telephone conversations and calls via other telecommunication
> > facilities may be recorded, including to comply with our legal and/or
> > regulatory requirements and/or to monitor the quality of our service.
> > For information about how we use your personal data, including your
> > legal rights, please refer to our privacy policy at:
> >
> https://eur03.safelinks.protection.ou

Re: Nifi putting object to S3 directory

[Peter Turcsanyi]

Hi Natalia,

Is the FlowFile transferred to the success or the failure relationship from
PutS3Object?

In general, you need to use dirtag/subdirtag /${filename}, so no leading
slash.
Leading slash results in a directory called '/' on S3.

Regards,
Peter Turcsanyi

On Mon, May 16, 2022 at 12:46 PM Fill, Natalia 
wrote:

> Hi Nifi Team,
>
> I am working on a solution to put file into S3 server. I used PutS3Object
> and managed to put some files into a bucket, but it failed to put files
> into specific directories on S3. No errors, but I don't see the files in
> the bucket. I used the following format for object key:
> /dirtag/subdirtag /${filename}. The tags do exist on S3.
>
> Does anyone have any suggestions how to put S3 object into specific
> directory and not just on top level in a bucket.
>
> Thanks
> Natalia
> This e-mail (and any attachments) may contain privileged and/or
> confidential information which may be protected by copyright or other
> intellectual property rights. If you are not the intended recipient please
> do not disclose, copy, distribute, disseminate or take any action in
> reliance on it. If you have received this e-mail in error please reply to
> the sender and then immediately delete it (including, any attachments).
> Should you wish to communicate with us by e-mail we cannot guarantee the
> security of any data outside our own computer systems or that any e-mail
> will be virus free.
>
> Any information contained in this e-mail may be subject to applicable
> terms and conditions and must not be construed as giving investment advice
> within or outside the United Kingdom or the Republic of Ireland.
>
> Telephone conversations and calls via other telecommunication facilities
> may be recorded, including to comply with our legal and/or regulatory
> requirements and/or to monitor the quality of our service. For information
> about how we use your personal data, including your legal rights, please
> refer to our privacy policy at:
> www.legalandgeneral.com/institutional/privacy-policy/.
>
> Legal & General Investment Management Limited (Company number 02091894),
> LGIM Real Assets (Operator) Limited (Company number 05522016), LGIM
> International Limited (Company number 07716001), Legal & General (Unit
> Trust Managers) Limited (Company number 01009418), GO ETF Solutions LLP
> (Company number OC329482) and LGIM Corporate Director Limited (Company
> number 07105051) are each authorised and regulated by the Financial Conduct
> Authority. All are registered in England & Wales with a registered office
> at One Coleman Street, London, EC2R 5AA.
>
> Legal and General Assurance (Pensions Management) Limited (Company number
> 01006112) is authorised by the Prudential Regulation Authority and
> regulated by the Financial Conduct Authority and the Prudential Regulation
> Authority. It is registered in England & Wales with a registered office at
> One Coleman Street, London, EC2R 5AA.
>
> Legal & General Property Limited (Registration number 02091897) is
> authorised and regulated by the Financial Conduct Authority for insurance
> mediation activities. It is registered in England & Wales with a registered
> office at One Coleman Street, London, EC2R 5AA.
>
> LGIM Managers (Europe) Limited is authorised and regulated by the Central
> Bank of Ireland (Reference No C173733). It is registered in the Republic of
> Ireland (Number 609677) with its principal business address at 33/34 Sir
> John Rogerson's Quay, Dublin 2, D02 XK09.
>
> The ultimate parent company is Legal & General Group PLC (Company number
> 01417162) which is registered in England & Wales and has a registered
> office at One Coleman Street, London, EC2R 5AA.
>
> 
>  This email has come from the internet and has been scanned for all
> viruses and potentially offensive content by Messagelabs on behalf of Legal
> & General 

Re: [VOTE] Release Apache NiFi 1.16.1

[Peter Turcsanyi]

+1 (non-binding)

Ran through the release helper. Built NiFi on Ubuntu 20.04 with Java 8
(jdk8u322-b06) and Java 11 (jdk-11.0.14.1+1).

Tested Stateless NiFi via ExecuteStateless and Kafka Connector using Java
8, 11 and 17 runtimes. Verified:
 - NIFI-9834: ExecuteStateless fails when the output FlowFile has no content
 - NIFI-9861: Stateless ClassLoader isolation does not work on Java 11

Regards,
Peter Turcsanyi

On Wed, Apr 27, 2022 at 9:02 PM Nathan Gough  wrote:

> +1 (non-binding), ran a 3 node cluster using external ZK with some simple
> test flows. Ran NiFi with Google OIDC auth. Checked hashes and other files.
>
> On Wed, Apr 27, 2022 at 10:24 AM Mike Thomsen 
> wrote:
>
> > +1 (binding) Ran a simple tika extraction flow on PDFs and DOCX files.
> > Worked fine. Saved that flow into the NiFi Registry.
> >
> > On Tue, Apr 26, 2022 at 4:47 PM Matt Burgess 
> wrote:
> > >
> > > +1 (binding)
> > >
> > > Ran through release helper, tested various flows including version
> > > control with the Registry, InvokeScriptedProcessor, Relationship
> > > retry, etc.  I did create [1] for MiNiFi but since there's a
> > > workaround it's not a dealbreaker IMO, I'm already working on it for
> > > 1.17.0.
> > >
> > > Thanks for RM'ing Joe!
> > >
> > > [1] https://issues.apache.org/jira/browse/NIFI-9967
> > >
> > > On Mon, Apr 25, 2022 at 2:29 PM Joe Witt  wrote:
> > > >
> > > > Hello,
> > > >
> > > > I am pleased to be calling this vote for the source release of Apache
> > NiFi
> > > > 1.16.1.
> > > >
> > > > The source zip, including signatures, digests, etc. can be found at:
> > > >
> https://repository.apache.org/content/repositories/orgapachenifi-1200
> > > >
> > > > The source being voted upon and the convenience binaries can be found
> > at:
> > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.16.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.16.1-RC1
> > > > The Git commit ID is 81166797e552b9d14b482807632f2f04321b2018
> > > >
> >
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=81166797e552b9d14b482807632f2f04321b2018
> > > >
> > > > Checksums of nifi-1.16.1-source-release.zip:
> > > > SHA256:
> > 2c39b45ba8eec42d601d5c9facad623d14660dd209c011b4a13b2b559b9f3e32
> > > > SHA512:
> > > >
> >
> cd670ab558937cac709dea0b4be3351559f57c9e9aedf54d5153706eee386a021262ef199e2bf9485763cf955931edfd6a24ca1c5a0748a77e3eeb91c490cbda
> > > >
> > > > 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
> > > >
> > > > 83 issues were closed/resolved for this release:
> > > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12351504
> > > > Release note highlights can be found here:
> > > >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.16.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.16.1
> > > > [ ] +0 no opinion
> > > > [ ] -1 Do not release this package because...
> >
>

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

[Peter Turcsanyi]

+1 (non-binding)

Ran through the release helper. Built NiFi on Ubuntu 20.04 with Java 8
(jdk8u322-b06) and Java 11 (jdk-11.0.14.1+1).
Executed some simple flows in traditional and stateless NiFi (incl. Kafka
Connect). Tested framework level retry.
Found an issue with ExecuteStateless but it does not seem to be a deal
breaker. Filed a jira for it [1].

Thanks for RMing, Joe!

Peter

[1] NIFI-9834 https://issues.apache.org/jira/browse/NIFI-9834

On Thu, Mar 24, 2022 at 6:30 PM Mark Bean  wrote:

> +1 (non-binding)
>
> Ran through steps in the helper guide. Built with various versions of Java:
> 8, 11 and 17. All were successful.
> Single instance, simple flow behaved as expected. Would like to run in a
> cluster environment, but may not have time to set that up before voting
> closes.
>
>
> On Mon, Mar 21, 2022 at 5:41 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&version=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...
> >
>

Re: [ANNOUNCE] New Apache NiFi Committer Paul Grey

[Peter Turcsanyi]

Congrats Paul!

On Thu, Mar 17, 2022 at 2:51 PM Mark Payne  wrote:

> Congrats Paul, welcome!
>
> > On Mar 17, 2022, at 9:41 AM, Mike Thomsen 
> wrote:
> >
> > Congrats, Paul!
> >
> > On Thu, Mar 17, 2022 at 9:26 AM Andrew Lim 
> wrote:
> >>
> >> Congrats Paul!
> >>
> >>> On Mar 17, 2022, at 2:17 AM, Chris Sampson 
> >>> 
> wrote:
> >>>
> >>> Congrats Paul, great to see your contributions.
> >>>
> >>>
> >>> Cheers,
> >>>
> >>> Chris Sampson
> >>>
> >>> On Thu, 17 Mar 2022, 01:36 Robert Fellows, 
> wrote:
> >>>
>  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: [VOTE] Release Apache NiFi 1.15.0

[Peter Turcsanyi]

-1 (non-binding)

NIFI-9235 [1] introduced a regression in PutHDFS due to
FileSystem.getAclStatus() calls [2]. This method is not supported on S3 and
it leads to error when PutHDFS is used with S3 (or with HDFS but no ACLs
enabled).

[1] https://issues.apache.org/jira/browse/NIFI-9235
[2]
https://github.com/apache/nifi/blob/main/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/src/main/java/org/apache/nifi/processors/hadoop/PutHDFS.java#L465

On Tue, Nov 2, 2021 at 9:28 PM Joe Gresock  wrote:

> +1 (non-binding)
>
> Ran through the release helper, tested a clustered flow, stood up
> nifi-registry and added a registry client to NiFi, version-controlled a
> processor group, verified several of the recent changes from JIRA.  Also
> ran a few Stateless flows.
>
> On Tue, Nov 2, 2021 at 8:52 AM Otto Fowler 
> wrote:
>
> >  +1
> >
> > Checked all the sources, hashes etc
> > Built and ran
> >
> > From: Joe Witt  
> > Reply: dev@nifi.apache.org  
> > Date: November 1, 2021 at 20:18:04
> > To: dev@nifi.apache.org  
> > Subject:  [VOTE] Release Apache NiFi 1.15.0
> >
> > Hello,
> >
> > I am pleased to be calling this vote for the source release of Apache
> > NiFi 1.15.0.
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > https://repository.apache.org/content/repositories/orgapachenifi-1185
> >
> > The source being voted upon and the convenience binaries can be found at:
> > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.15.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.15.0-RC2
> > The Git commit ID is c48d10315976805f6e675fc7907dfe196787e4bc
> >
> >
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=c48d10315976805f6e675fc7907dfe196787e4bc
> >
> > Checksums of nifi-1.15.0-source-release.zip:
> > SHA256: 9db0c22da32840320c06df3bca75c22440aa2b1bfae42a249b4850c3ce89f8e4
> > SHA512:
> >
> >
> 866a6dfdd9a843a27f34d1d4842f056cc82a1e17852f03fb90aa489d5e1adc26e8f7a6da07fdaf2de73c10580e0236eea528c3b5119d98fb9ddbd3f2cd9d2688
> >
> >
> > 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
> >
> > 232 issues were closed/resolved for this release:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12350382
> >
> > Release note highlights can be found here:
> >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.15.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.15.0
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
> >
>

Re: [ANNOUNCE] New NiFi PMC Member David Handermann

[Peter Turcsanyi]

Congrats, David!

On Mon, Sep 20, 2021 at 8:19 PM Otto Fowler  wrote:

>  Congratulations!
>
> From: Bryan Bende  
> Reply: dev@nifi.apache.org  
> Date: September 17, 2021 at 08:56:43
> To: dev@nifi.apache.org  
> Subject:  [ANNOUNCE] New NiFi PMC Member David Handermann
>
> NiFi Community,
>
> On behalf of the Apache NiFI PMC, I am very pleased to announce that
> David Handermann has accepted the PMC's invitation to join the Apache
> NiFi PMC.
>
> David has made significant improvements in a number of security
> related areas, he continues to improve the stability of our tests and
> CI builds, and regularly helps out the community through the mailing
> lists, Slack, and PR reviews.
>
> Please join us in congratulating and welcoming David to the Apache NiFi
> PMC.
>
> Congratulations David!
>

Re: Problem with variables in 1.14

[Peter Turcsanyi]

Hi Eduardo,

Thanks for the detailed test cases.
Actually, I did not test it with NiFi Registry but I will.

Also thanks for creating the jira. I will take care of it.

Peter

On Fri, Sep 10, 2021 at 12:52 PM Eduardo Fontes 
wrote:

> Hi Peter,
>
> Thanks for reply.
> I've tested it again and you are half-right. kkk
> 1) If I use a non-existing variable, a got error;
> 2) If I use an existing variable, it's ok, BUT;
> 3) If I use an existing variable AND commit the flow to the NiFi Registry,
> I can't import that flow anymore. I got same error as case #1;
> 4) If same case as #3, I can import a early version (without import
> problems), then "change version" to the problematic one, it works fine.
> Seems the issue is when creating new components with variable references in
> the import process, along with using non-existing variable in UI.
>
> I've tested with processors and other controller services, and with other
> properties in DBCPConnectionPool, but it seems to be a very specific issue
> with property "Database Driver Location(s)" in DBCPConnectionPool
> controller service.
> I'll open a JIRA for this.
>
> Thanks.
> Eduardo Fontes
>
> On Fri, Sep 10, 2021 at 5:21 AM Peter Turcsanyi 
> wrote:
>
> > Hi Eduardo,
> >
> > I managed to replicate the issue with a non-existing variable reference
> but
> > it properly works for me if the variable exists.
> > Could you please double check it on your side?
> >
> > The non-existing variable case is definitely an issue that could have
> been
> > brought in with NIFI-8206 or NIFI-8429 (further investigation needed to
> > identify the root cause).
> >
> > Regards,
> > Peter Turcsanyi
> >
> > On Thu, Sep 9, 2021 at 11:14 PM Eduardo Fontes  >
> > wrote:
> >
> > > Hi all,
> > >
> > > Can someone test a thing in NiFi 1.14?
> > >
> > > 1) Create a DBCPConnectionPool in a Process Group;
> > > 2) In property "Database Driver Location(s)"set any variable (existing
> or
> > > not), like ${teste-var};
> > > 3) Click Apply
> > >
> > > To me, the UI give error but save the value. If I commit this in NiFi
> > > Registry, I can not import the flow.
> > >
> > > Somebody tell me if this happens only with my system or not, please.
> > >
> > > Thanks so much.
> > > Eduardo Fontes
> > >
> >
>

Re: Problem with variables in 1.14

[Peter Turcsanyi]

Hi Eduardo,

I managed to replicate the issue with a non-existing variable reference but
it properly works for me if the variable exists.
Could you please double check it on your side?

The non-existing variable case is definitely an issue that could have been
brought in with NIFI-8206 or NIFI-8429 (further investigation needed to
identify the root cause).

Regards,
Peter Turcsanyi

On Thu, Sep 9, 2021 at 11:14 PM Eduardo Fontes 
wrote:

> Hi all,
>
> Can someone test a thing in NiFi 1.14?
>
> 1) Create a DBCPConnectionPool in a Process Group;
> 2) In property "Database Driver Location(s)"set any variable (existing or
> not), like ${teste-var};
> 3) Click Apply
>
> To me, the UI give error but save the value. If I commit this in NiFi
> Registry, I can not import the flow.
>
> Somebody tell me if this happens only with my system or not, please.
>
> Thanks so much.
> Eduardo Fontes
>

Re: [discuss] nifi 1.14.0

[Peter Turcsanyi]

There is an ongoing PR about disabling LongRunningTaskMonitor by default
(NIFI-8645). I believe I addressed all review comments so it will be merged
soon.
Could we include it in 1.14?

Thanks,
Peter Turcsanyi

On Fri, Jun 11, 2021 at 10:05 PM Joe Witt  wrote:

> So. Dang. Cool.  I just built from latest main and poof - I'm on https
> with username/password.
>
> Will start whipping up the process for an RC.  Probably will be a
> little slow going with dayjob factors but will get on it.
>
> Thanks
>
> On Fri, Jun 11, 2021 at 12:14 PM David Handermann
>  wrote:
> >
> > Thanks to Mark Payne, NIFI-8516 is now merged, so that covers current
> open
> > issues around securing the default configuration.
> >
> > Regards,
> > David Handermann
> >
> > On Fri, Jun 11, 2021 at 11:55 AM David Handermann <
> > exceptionfact...@apache.org> wrote:
> >
> > > Joe,
> > >
> > > Thanks for following up.  The PR for NIFI-8516 has gone through several
> > > rounds of feedback, I believe it is about ready to go, pending
> confirmation
> > > that the ability to set custom credentials addresses the ease of use
> > > concern.
> > >
> > > Regards,
> > > David Handermann
> > >
> > > On Fri, Jun 11, 2021 at 11:41 AM Joe Witt  wrote:
> > >
> > >> David,
> > >>
> > >> Ok thanks - do you have a sense of when what you see as good 1.14
> > >> specific work will be merged?  Do you have the reviewers/engagement
> > >> you need?
> > >>
> > >> This 1.14 is already pretty packed but definitely agree we need to
> > >> make real progress on secure by default and this release is a great
> > >> time to take the first big step.
> > >>
> > >> Thanks
> > >>
> > >> On Mon, May 31, 2021 at 5:52 AM David Handermann
> > >>  wrote:
> > >> >
> > >> > Thanks for kicking off the discussion Joe!
> > >> >
> > >> > Of the many items that could be included in the next release,
> securing
> > >> the
> > >> > default configuration as described in NIFI-8220
> > >> > <https://issues.apache.org/jira/browse/NIFI-8220> would be great to
> > >> have
> > >> > completed.  Most of the elements are in place, and the current Pull
> > >> Request
> > >> > for NIFI-8516 <https://github.com/apache/nifi/pull/5068> is under
> > >> review.
> > >> > If there are any other achievable items that should be included as
> part
> > >> of
> > >> > a secure default installation for NiFi, it would be helpful to add
> > >> > sub-tasks to NIFI-8220.  The current scope is limited to a
> standalone
> > >> > installation, so issues regarding clustered deployments can be
> handled
> > >> > separately.  If others are interested in evaluating the proposed new
> > >> > default configuration that requires HTTPS and leverages a generated
> > >> > username and password, feel free to provide feedback on NIFI-8516.
> > >> >
> > >> > Regards,
> > >> > David Handermann
> > >> >
> > >> > On Thu, May 27, 2021 at 6:51 PM Otto Fowler <
> ottobackwa...@gmail.com>
> > >> wrote:
> > >> >
> > >> > > I think NIFI-8625 and NIFI-8461 need to be understood and
> addressed.
> > >> > >
> > >> > >
> > >> > > > On May 27, 2021, at 13:29, Joe Witt  wrote:
> > >> > > >
> > >> > > > Team,
> > >> > > >
> > >> > > > There has been a tremendous amount of work already on the 1.14
> line
> > >> as
> > >> > > shown:
> > >> > > >
> > >> > > > https://issues.apache.org/jira/projects/NIFI/versions/12349644
> > >> > > >
> > >> > > > These include merging the nifi registry and minifi java into the
> > >> nifi
> > >> > > > line itself.  So when we release these things stay in sync and
> > >> > > > maintained.  The release will now produce things like Apache
> NiFi,
> > >> the
> > >> > > > Apache NiFi toolkit, Apache NiFi Registry, and Apache NiFi
> MiNiFi
> > >> Java
> > >> > > > and the Apache NiFi stateless runtime as well.  There have been
> many
> > >> > > > improvements to core nifi and stateless nifi now meaning we
> have the
> > >> > > > traditional execution form factor and this new stateless mode.
> We
> > >> can
> > >> > > > now hot load nars from HDFS storage locations which could mean
> HDFS,
> > >> > > > blob storage in the cloud, etc..  There is a lot more.
> > >> > > >
> > >> > > > Anyway, I wanted to start circling the wagons for a 1.14
> release.
> > >> I'm
> > >> > > > happy to take on RM duties especially since there will be new
> > >> elements
> > >> > > > to the release process.
> > >> > > >
> > >> > > > Thanks
> > >> > >
> > >> > >
> > >>
> > >
>

Re: [VOTE] Release Apache NiFi 1.13.1

[Peter Turcsanyi]

+1 (non-binding)

Went through the release helper guide.
Verified full build with empty local maven repo with Java 8 (AdoptOpenJDK
1.8.0_282-b08) and 11 (AdoptOpenJDK 11.0.10+9) on Ubuntu 20.04.
Ran some test flows.


I found 2 Jira tickets with Fix Version 1.13.1 which are not present in the
release:
- NIFI-8258: Add support for Service Principal authentication in ADLS
processors [1]
- NIFI-8286: CertificateUtils do not support embedded emailAddress in CN [2]

I don't think it is critical but the jiras need to be adjusted.


Thanks,
Peter

[1] https://issues.apache.org/jira/browse/NIFI-8258
[2] https://issues.apache.org/jira/browse/NIFI-8286

On Sun, Mar 14, 2021 at 5:44 AM Andrew Lim 
wrote:

> +1 (binding)
>
> -Tested secure NiFi with secure NiFi Registry 0.8.0
> -Ran basic flows successfully
> -Tested basic versioned flow functionality
> -Reviewed and tested Core UI fixes and Documentation updates
>
> Drew
>
> > On Mar 11, 2021, at 11:29 AM, Joe Witt  wrote:
> >
> > Hello,
> >
> > I am pleased to be calling this vote for the source release of Apache
> NiFi
> > 1.13.1.
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > https://repository.apache.org/content/repositories/orgapachenifi-1179
> >
> > The source being voted upon and the convenience binaries can be found at:
> > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.13.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.13.1-RC1
> > The Git commit ID is acbc217cb7002d7489421f4d346b995a43b6ea01
> >
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=acbc217cb7002d7489421f4d346b995a43b6ea01
> >
> > Checksums of nifi-1.13.1-source-release.zip:
> > SHA256: 0a397df640e579720e26699e38a3738c5be05af01aad8aaeefc04eb58591faac
> > SHA512:
> >
> 7f8df759d4345ccd6e75c169bd0aab1b7f4f64bf5a8b11b45bc1d7c8163acd0035922dcdbef232392279f4ea0710d4a97c55d480281bfe1d50b6401295633d48
> >
> > 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
> >
> > 48 issues were closed/resolved for this release:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12348700
> >
> > Release note highlights can be found here:
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.13.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.13.1
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
>
>

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

[Peter Turcsanyi]

+1 non-binding

Went through the release helper guide.
Verified full build with empty local maven repo with Java 8 (AdoptOpenJDK
1.8.0_282-b08) and 11 (AdoptOpenJDK 11.0.10+9) on Ubuntu 20.04.
Ran full builds with different time zone settings to verify NIFI-8023, also
tested it with flows.
Ran some SSL related test flows with processors changed recently
(ListenHTTP, GRPC, MQTT).
Verified --wait-for-init on Ubuntu and CentOS.
Verified NiFi web server listening on localhost only by default.

Thanks,
Peter

On Sun, Feb 14, 2021 at 12:56 AM David Handermann <
exceptionfact...@gmail.com> wrote:

> +1 non-binding
>
> Verified release signatures and expected files.
> Verified build on Ubuntu 20.10 using Apache Maven 3.6.3 with Azul Zulu JDK
> 11.0.10 and AdoptOpenJDK 1.8.0_282.
> Verified absence of startup script shell warnings on Ubuntu 20.10.
> Verified service listening on localhost when using default nifi.properties.
> Configured and tested mutual TLS authentication on a standalone server with
> BCFKS key store and trust store.
>
> Regards,
> David Handermann
>
> On Fri, Feb 12, 2021 at 5:45 PM Muazma Zahid  wrote:
>
> > +1 (non-binding)
> >
> > - Ran build with OpenJDK 1.8.0_275 on Linux
> > - Deployed cluster on Azure and tested flows with Blob, ADLS, and
> CosmosDB
> > processors.
> >
> > Looks good to me.
> >
> > Thanks
> > Muazma
> >
> > On Fri, Feb 12, 2021 at 3:38 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 Fri, Feb 12, 2021 at 2:13 PM Marc Parisi 
> wrote:
> > >
> > > > +1
> > > > - Verified sigs and hashes
> > > > - Built on PopOS w/ java 8 && 11
> > > > - Tested with basic flow sending data to various devices w/ Secured
> > > > transport
> > > > - Tested secured w/ secured nifi reg.
> > > >
> > > > Thanks,
> > > > Marc
> > > >
> > > > On Fri, Feb 12, 2021 at 2:56 PM Andrew Lim <
> andrewlim.apa...@gmail.com
> > >
> > > > wrote:
> > > >
> > > > > +1 (binding)
> > > > >
> > > > > -Tested secure NiFi with secure NiFi Registry 0.8.0
> > > > > -Ran basic flows successfully
> > > > > -Tested basic versioned flow functionality
> > > > > -Reviewed and tested Core UI fixes and Documentation updates
> > > > >
> > > > > Drew
> > > > >
> > > > > > On Feb 10, 2021, at 11:37 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-1178
> > > > > >
> > > > > > 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-RC4
> > > > > > The Git commit ID is 3bc6a122091214b33eee17a270163d7ca26e2a0c
> > > > > >
> > > > >
> > > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=3bc6a122091214b33eee17a270163d7ca26e2a0c
> > > > > >
> > > > > > Checksums of nifi-1.13.0-source-release.zip:
> > > > > > SHA256:
> > > > 95efe5db38e973c9f4062a7b2c95fdc5dad31d7c5e1d36ce1776b9b227c89b9c
> > > > > > SHA512:
> > > > > >
> > > > >
> > > >
> > >
> >
> d7dd9e851341ebd605784142a7861935f6f814bc612499013456a15713bc9119e426df8f26445c260bdb25cbfc21822cf0d44985bf372a065c9d8597953a3c4a
> > > > > >
> > > > > > 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
> > > > > >
> > > > > > 260 issues were closed/resolved for this release:
> > > > > >
> > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12348700
> > > > > >
> > > > > > Release note highlights can be found here:
> > > > > >
> > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.13.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.13.0
> > > > > > [ ] +0 no opinion
> > > > > > [ ] -1 Do not release this package because...
> > > > >
> > > > >
> > > >
> > >
> >
>

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

[Peter Turcsanyi]

+1 non-binding

Went through the release helper guide.
Verified full build with empty local maven repo with Java 8 (AdoptOpenJDK
1.8.0_282-b08) and 11 (AdoptOpenJDK 11.0.10+9) on Ubuntu 20.04.
Ran full builds with different time zone settings to verify NIFI-8023, also
tested it with flows.
Ran some SSL related test flows with processors changed recently
(ListenHTTP, GRPC, MQTT).

Thanks for RMing Joe!

On Tue, Feb 2, 2021 at 6:04 PM Otto Fowler  wrote:

> +1
> Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
> Maven home: /usr/local/Cellar/maven/3.6.3_1/libexec
> Java version: 1.8.0_282, vendor: AdoptOpenJDK, runtime:
> /Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.16", arch: "x86_64", family: “mac"
>
> Thanks Joe!
>
>
> > On Feb 1, 2021, at 20:10, 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 nifi-1.13.0-source-release.zip:
> > SHA256: 4913dd3d943afac710d1a277bf31beebf7a6207a20e1148849d69511f44fc97b
> > SHA512:
> >
> dc9935f0eb8692cd8493f5863bc8ae2ef0b52653fa69ff8b9a7e8db7dbd9ec6561f6ffdca4a1b55e43b289d04f5671f5ab4de30999838c5fca5c282c00a7c7f8
> >
> > 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
> >
> > 238 issues were closed/resolved for this release:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12348700
> >
> > Release note highlights can be found here:
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.13.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.13.0
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
>
>

Re: [DISCUSS] Release of Apache NiFi 1.13.0

[Peter Turcsanyi]

There is one more ongoing PR to fix some Date related test failures which
occur when the build is started in a UTC+ time zone.
It should be fixed and merged before the release.

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

Thanks,
Peter Turcsanyi

On Wed, Jan 13, 2021 at 3:11 AM Mark Payne  wrote:

> Eduardo,
>
> I plan to review this PR tomorrow. Assuming that all is good, I should
> have it merged in.
>
> Thanks
> -Mark
>
> Sent from my iPhone
>
> > On Jan 12, 2021, at 8:24 PM, Eduardo Fontes 
> wrote:
> >
> > Hi,
> >
> > Is it possible include https://issues.apache.org/jira/browse/NIFI-7973 (
> > https://github.com/apache/nifi/pull/4682) in 1.13.0 release?
> >
> > Thanks!
> > Eduardo Fontes
> >
> >> On Tue, Jan 12, 2021 at 3:18 PM Pierre Villard <
> pierre.villard...@gmail.com>
> >> wrote:
> >>
> >> Hi all,
> >>
> >> Current status about what we want to get in based on this thread:
> >> - NIFI-8034 - PropertyValue.isExpressionLanguagePresent always returns
> true
> >> for non-null values - https://github.com/apache/nifi/pull/4746
> >> - NIFI-7989 - Add Hive "data drift" processor -
> >> https://github.com/apache/nifi/pull/4750
> >> - NIFI-7356 - TLS + embedded Zookeeper - pull request to be submitted by
> >> Nathan
> >>
> >> If we can wrap up these JIRAs, we could get a release candidate for NiFi
> >> 1.13 soon.
> >>
> >> Thanks,
> >> Pierre
> >>
> >>
> >>
> >> Le mer. 6 janv. 2021 à 04:17, Joey Frazee  .invalid>
> >> a écrit :
> >>
> >>> I have https://github.com/apache/nifi/pull/4632 which fixes an OOME in
> >>> PutAzureBlobStorage reported in
> >>>
> >>
> https://lists.apache.org/x/thread.html/rdef82be24828277b85bdc94dc57a8fb9df6f73552daeda289c941a51%40%3Cusers.nifi.apache.org%3E
> >>>
> >>> It’s a pretty small change.
> >>>
> >>> -joey
> >>>
> >>>> On Jan 5, 2021, at 3:14 PM, Matt Burgess  wrote:
> >>>>
> >>>> I am reviewing a PR at the moment but intend to review the graph
> stuff
> >>> right afterwards.
> >>>>
> >>>>> On Jan 5, 2021, at 5:35 PM, Mike Thomsen 
> >>> wrote:
> >>>>>
> >>>>> I have a PR for graph that we need to close out because part of the
> >>> graph
> >>>>> bundle will be broken without it.
> >>>>>
> >>>>>>> On Tue, Jan 5, 2021, 11:50 Mark Bean 
> wrote:
> >>>>>>
> >>>>>> I'd like to see this PR completed as well
> >>>>>> https://github.com/apache/nifi/pull/4225
> >>>>>>
> >>>>>> There's been discussion on it, and I don't see any further
> >> objections.
> >>>>>>
> >>>>>> Thanks,
> >>>>>> Mark
> >>>>>>
> >>>>>> On Thu, Nov 26, 2020 at 4:55 AM Pierre Villard <
> >>>>>> pierre.villard...@gmail.com>
> >>>>>> wrote:
> >>>>>>
> >>>>>>> Hi community,
> >>>>>>>
> >>>>>>> Starting a discussion thread around the release of NiFi 1.13.0. We
> >>> added
> >>>>>>> quite a lot of significant improvements and features since the
> >>> release of
> >>>>>>> 1.12.1 - I see 143 JIRAs with 1.13.0 as the fix version. I think it
> >>> makes
> >>>>>>> sense to consider a new release.
> >>>>>>>
> >>>>>>> Please share here the JIRAs with opened pull requests that we would
> >>> need
> >>>>>> to
> >>>>>>> look at to make this release happen.
> >>>>>>>
> >>>>>>> Thanks,
> >>>>>>> Pierre
> >>>>>>>
> >>>>>>
> >>>
> >>
>

Re: [DISCUSS] Release of Apache NiFi 1.13.0

[Peter Turcsanyi]

There is a bug in PropertyValue::isExpressionLanguagePresent we should fix
for the next release:

PropertyValue.isExpressionLanguagePresent always returns true for non-null
values
https://issues.apache.org/jira/browse/NIFI-8034


On Tue, Jan 5, 2021 at 5:49 PM Mark Bean  wrote:

> I'd like to see this PR completed as well
> https://github.com/apache/nifi/pull/4225
>
> There's been discussion on it, and I don't see any further objections.
>
> Thanks,
> Mark
>
> On Thu, Nov 26, 2020 at 4:55 AM Pierre Villard <
> pierre.villard...@gmail.com>
> wrote:
>
> > Hi community,
> >
> > Starting a discussion thread around the release of NiFi 1.13.0. We added
> > quite a lot of significant improvements and features since the release of
> > 1.12.1 - I see 143 JIRAs with 1.13.0 as the fix version. I think it makes
> > sense to consider a new release.
> >
> > Please share here the JIRAs with opened pull requests that we would need
> to
> > look at to make this release happen.
> >
> > Thanks,
> > Pierre
> >
>

Re: urgent Info required on configure Maximum Timer Driven Thread Count

[Peter Turcsanyi]

Hi Ganesh,

The default setting is 10.
A typical setting is 2 x CPU cores on your machine.
It is used here in the code:
https://github.com/apache/nifi/blob/c29cced269dcce28fb9ba034025d01e76a79b037/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/FlowController.java#L249

I hope this helps. Not sure which one you are interested in.

Best,
Peter Turcsanyi

On Wed, Dec 2, 2020 at 7:51 AM Ganesh, B (Nokia - IN/Bangalore) <
b.gan...@nokia.com> wrote:

> Hi ,
>
>
>
> The default of Maximum Timer Driven Thread Count  is set to 10 , I could
> not find the place or file which we are using that value 10 .
>
>
>
> Could ypu please help me to get that default configuration setting ?
>
>
>
> Thanks & Regards,
>
> Ganesh.B
>
>
>
>
>
>
>
>

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

[Peter Turcsanyi]

+1 (non-binding)

- verified checksums and signatures
- built source (empty local maven repo, AdoptOpenJDK 1.8.0_265 on Ubuntu
20.04)
- untar and ran the provided convenience binary
- tested some simple flows, check NIFI-7794 (fixed regression in
PutAzureBlobStorage)

Peter

On Fri, Sep 25, 2020 at 11:38 AM Kotaro Terada  wrote:

> +1 (non-binding)
>
> Verified signatures and hashes.
> Built with OpenJDK 1.8 and OpenJDK 11.
> Set up a secure 3-node cluster.
> Tested some dataflows.
> Confirmed that it works fine with multiple SAN.
>
> Thanks,
> Kotaro
>
>
> On Fri, Sep 25, 2020 at 8:45 AM Robert Fellows 
> wrote:
>
> > +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&version=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.1

[Peter Turcsanyi]

+1 (non-binding)

- verified checksums and signatures
- built source (empty local maven repo, AdoptOpenJDK 1.8.0_265 on Ubuntu
18.04.5), start up the binary
- untar and ran the convenience binary too
- tested some simple flows, including NIFI-7760 (fixed regression in
UnpackContent)

Peter

On Thu, Sep 10, 2020 at 2:31 AM Joey Frazee 
wrote:

> +1 (non-binding)
> Verified checksums and signatures
> Ran full build with contrib check on Linux and Zulu OpenJDK 11.0.7
> Tested TLS toolkit and secure cluster with multiple SANs
>
> -joey
> On Sep 9, 2020, 8:51 AM -0700, Kevin Doran , wrote:
> > +1 (binding)
> >
> > - Checked hashes/sigs
> > - L&N is present
> > - Built from source and built docker images from resulting artifacts
> > - Ran a docker compose environment with NiFi Registry 0.7.0 and NiFi
> 1.12.1 RC1
> > - Tested flow authoring and Registry integration in the test environment
> >
> > One thing to note is that running the docker profile from the
> decompressed source distribution still results in some build errors due to
> shell scripts we use for our docker container tests not being executable.
> At some point we should look into improving our release process to try to
> preserve those permissions, our making our build plugins robust enough that
> those permissions are not required at build time.
> >
> > Kevin
> >
> > > On Sep 9, 2020, at 10:48, Bryan Bende  wrote:
> > >
> > > +1 (binding)
> > >
> > > Ran through the release helper and everything looks good, used 1.12.1
> > > toolkit to generate certs for a secure instance.
> > >
> > > On Tue, Sep 8, 2020 at 11:36 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
> > > >
> > > > Drew
> > > >
> > > > > On Sep 8, 2020, at 12:59 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-1167
> > > > >
> > > > > 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-RC1
> > > > > The Git commit ID is e8f708b3945183b7ab1b356c00d0fcbd929d6163
> > > > >
> > > >
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=e8f708b3945183b7ab1b356c00d0fcbd929d6163
> > > > >
> > > > > Checksums of nifi-1.12.1-source-release.zip:
> > > > > SHA256:
> 6fa7e4389ff33957133292e9749876affe1258e6f30d4e60b53e8c2d01d032cb
> > > > > SHA512:
> > > > >
> > > >
> fee615ee885b05a290a4d6c7399ecf0b70a93cc1d5d9b019c7840ceb89d3279a540da4de75765c589c301fff751e62c9e15cc33d078b5fad03bbbd28e74f8ea9
> > > > >
> > > > > 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
> > > > >
> > > > > 19 issues were closed/resolved for this release:
> > > > >
> > > >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=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...
> > > >
> > > >
> >
>

Re: [VOTE] Release Apache NiFi 1.12.0

[Peter Turcsanyi]

+1 (non-binding)

- verified checksums and signatures
- built source (empty local maven repo, Java 8 and 11 on Linux), start up
the binary
- untar and ran the convenience binary, tested ADLS processors and other
simple flows

On Mon, Aug 17, 2020 at 11:07 AM Pierre Villard 
wrote:

> +1 (binding)
>
> Went through the usual steps. Deployed a secured cluster on GCP and tried a
> few flows. Confirmed some fixes, tested the ScriptedTransformRecord
> processor, and the new flowfile concurrency features.
>
> Thanks all for this great release, a lot of really good stuff!
> Thanks Joe for taking care of the release management!
>
> Le lun. 17 août 2020 à 05:03, Chad Zobrisky  a écrit
> :
>
> > +1 (non-binding)
> >
> > Ran through the release helper, everything looks good.
> > Full build on java8 in wsl, ubuntu.
> > Verified basic functionality in single node and 5 cluster docker
> > configuration.
> >
> > - Chad
> >
> >
> > On Sat, Aug 15, 2020 at 7:26 AM Marc Parisi  wrote:
> >
> > > +1 (binding )
> > >
> > > Ran through helper guide with clean build env . Ran flows that ingest
> and
> > > query Apache hbase and accumulo from a 10 VM secured cluster in my
> local
> > > environment with jdk11.
> > >
> > > Thanks,
> > > Marc
> > >
> > >
> > > On Sat, Aug 15, 2020, 7:11 AM Kotaro Terada 
> wrote:
> > >
> > > > +1 (non-binding)
> > > >
> > > > Verified signatures and hashes.
> > > > Built an RPM package with OpenJDK 11.0.8 on CentOS 7.8.
> > > > Set up a 3-node cluster.
> > > > Tested several flows.
> > > >
> > > > Thanks,
> > > > Kotaro
> > > >
> > > >
> > > > On Sat, Aug 15, 2020 at 5:09 PM Joey Frazee  > > > .invalid>
> > > > wrote:
> > > >
> > > > > +1 (non-binding)
> > > > >
> > > > > Verified commit id, checksums, and signatures
> > > > > Successfully built and ran tests on Linux with Java 1.8.0_252 and
> > Java
> > > > > 11.0.7 2020-04-14 and on macOS with Java 11.0.6 2020-01-14 LTS
> > > > > Ran data flows on standalone and cluster
> > > > > Verified JMS improvements, InvokeHTTP changes, and Azure
> integration
> > in
> > > > > commercial and gov regions
> > > > >
> > > > > -joey
> > > > > On Aug 14, 2020, 1:31 PM -0700, Robert Fellows <
> > rob.fell...@gmail.com
> > > >,
> > > > > wrote:
> > > > > > + 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 <
> > > > > andrewlim.apa...@gmail.com>
> > > > > > > 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+Apa

Re: [ANNOUNCE] New Apache NiFi Committer Marton Szasz

[Peter Turcsanyi]

Congrats Marton!

On Mon, Aug 3, 2020 at 10:02 AM Arpad Boda  wrote:

> Apache NiFi community,
>
> On behalf of the Apache NiFI PMC, I am very pleased to announce that Marton
> has accepted the PMC's invitation to become a committer on the Apache NiFi
> project. We greatly appreciate all of Marton's hard work and generous
> contributions to the project. We look forward to continued involvement in
> the project.
>
> Marton had more than 100 contributions to MiNiFi C++ this year in various
> areas: from Windows-specific memory leaks to nice new features and a lot of
> code reviews. He also showed active presence on the mailing list helping
> out the community.
>
> Welcome and congratulations!
>

Re: [VOTE] Release Apache NiFi Registry 0.7.0

[Peter Turcsanyi]

+1 (non-binding)

- verified signatures and checksums
- built with Java 8 (empty local maven repo, OS: Ubuntu 18)
- run NiFi Registry and connected to it from NiFi 1.11.4 (unsecure),
performed some tests
- download the convenience binary and tested a few things on it too

Thanks,
Peter

On Fri, Jul 17, 2020 at 7:20 PM Marton Szasz  wrote:

> +1 (non-binding)
>
> Followed the verification guide, migrated a test deployment using
> GitFlowPersistenceProvider from 0.6.0, then tested MiNiFi C++ C2 flow
> update using the new registry version.
>
> Thanks,
> Marton
>
> On Fri, 17 Jul 2020 at 18:36, Mark Payne  wrote:
>
> > +1 (binding)
> >
> > Verified full build with contrib check, deployed and performed some
> tests,
> > verifying that the FlowFiles concurrency and outbound policy was properly
> > stored and retrieved.
> >
> > Thanks
> > -Mark
> >
> >
> > > On Jul 17, 2020, at 11:55 AM, Pierre Villard <
> > pierre.villard...@gmail.com> wrote:
> > >
> > > +1 (binding)
> > >
> > > * went through the usual release verification steps (signatures, build,
> > > contrib check, licenses)
> > > * deployed a local NR 0.7.0 instance with a single local NiFi
> > > 1.12.0-SNAPSHOT (non secure)
> > >
> > > Thanks Bryan for taking care of this!
> > >
> > > Le ven. 17 juil. 2020 à 17:46, Matt Burgess  a
> > écrit :
> > >
> > >> +1 (binding), verified hashes and commit ID, tested a few things on an
> > >> unsecured instance. Thanks for RM'ing Bryan!
> > >>
> > >> 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&version=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...
> > >>
> >
> >
>

Re: [nifi] branch main created (now 239a2e8)

[Peter Turcsanyi]

It is also possible to edit the existing PR on github and simply change the
base branch to apache/main.

On Tue, Jul 7, 2020 at 10:21 PM Otto Fowler  wrote:

>  What I did was to rebase -i on upstream main and force push.
> Then in the PR reset the base to main
>
> On July 7, 2020 at 16:01:28, Andy LoPresto (alopre...@apache.org) wrote:
>
> The PRs should be mergeable to main automatically as I _moved_ the branch
> rather than copying it, so unless there are new code conflicts, there
> shouldn’t be a problem. There are tools from other developers [1] which can
> automate the process of rebasing, but in general I don’t think this is
> necessary. br/> <
> For anyone who wishes to relabel their local working copy branches, you can
> follow these instructions from [2]. br/> <
> If someone has a local clone, then can update their locals <
> https://twitter.com/xunit/status/1269881005877256192> like this:
>
> $ git checkout master
> $ git branch -m master main
> $ git fetch
> $ git branch --unset-upstream
> $ git branch -u origin/main
> $ git symbolic-ref refs/remotes/origin/HEAD refs/remotes/origin/main
>
>
> I will send new updates when the other NiFi subprojects (Registry, MiNiFi
> Java, MiNiFi C++, and FDS) have had their default branches renamed. br/> <
> [1] https://github.com/ethomson/retarget_prs <
> https://github.com/ethomson/retarget_prs>
> [2]
>
> https://www.hanselman.com/blog/EasilyRenameYourGitDefaultBranchFromMasterToMain.aspx
> <
>
> https://www.hanselman.com/blog/EasilyRenameYourGitDefaultBranchFromMasterToMain.aspx
> >
>
>
>
> Andy LoPresto
> alopre...@apache.org
> alopresto.apa...@gmail.com
> He/Him
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
>
> > On Jul 7, 2020, at 9:14 AM, Matt Burgess  wrote:
> > br/>> IMO that's a yes, the branch is created and noww main has more
> commits
> > than master and is the "source of truth". We should be using main as
> > the default branch (the way it is in Github now), rebasing PRs atop
> > main and changing the PRs in Github to have main as the base branch
> > (so no mistakes are made when merging). With any luck master just kind
> > of fades away, or perhaps at some point we just delete it.
> > br/>> With some scripting we should be able to automaate such PR updates,
> but
> > personally it felt a little heavy-handed so I haven't written said
> > script(s). Instead I'm just updating my own PRs and when I review
> > someone's, I'm leaving a comment to please switch over to main as the
> > base branch (both in the code and the PR).
> > br/>> That's just my two cents though, happy to discuuss further. I think
> we
> > really just need to avoid updating the master branch from here on out
> > rather than trying to keep them in sync, or even worse having them
> > diverge each with new commits that aren't in the other.
> > br/>> Regards, <
> > Matt
> > br/>> On Tue, Jul 7, 2020 at 12:06 PM Otto FFowler <
> ottobackwa...@gmail.com> wrote:
> >> br/>>> So, is that a yes??
> >> br/>>> On July 7, 2020 at 10:53:59, Matt Burgeess (mattyb...@apache.org
> )
> wrote:
> >> br/>>> Thanks Mike!! I rebased against main since that's our default
> branch
> >> from now on, so should be ok now.
> >> br/>>> On Tue, Jul 7, 2020 at 10:52 AM Mike Thhomsen <
> mikerthom...@gmail.com>
> >> wrote:
> >>> br/ I'll take it. <
> >>> br/ On Tue, Jul 7, 2020 at 9:57 AMM Matt Burgess <
> mattyb...@apache.org> wrote:
> >>> br/> I've got a PR [[1] that's approaching 1.5 years since the last
> update,
>  but it should be good to go and fairly straightforward to test, any
>  takers? :) I just rebased it against the laster master branch, should
>  I be using main as of this point, or is there more work to be done
>  before we switch over?
>  br/> Thanks, <
>  Matt
>  br/> [[1] https://github.com/apache/nifi/pull/2718
>  br/> On Tue, Jul 7, 2020 at 5:48 AM Mike Thomsen <
> mikerthom...@gmail.com>
>  wrote:
> > br/>> Might also be aa good time to think about closing out old
> PRs (like
> >> age >
> > 1.5 years).
> > br/>> On Mon, Jul 6, 2020 at 10:49 PM Otto Fowler <
> ottobackwa...@gmail.com>
>  wrote:
> > br/>>> So, should we rebase our outstanding PR’s? Should all
> outstanding
>  PR’s
> >> get a note?
> >> br/>>> On Julyy 6, 2020 at 17:57:25, Andy LoPresto (
> alopre...@apache.org)
>  wrote:
> >> br/>>> Apache Infra completed the change. Everything looks ok
> from my end
> >> but
>  as I
> >> made the initial change, can someone else verify that their local
> >> repo
>  is
> >> good to go? Once that’s done, I’ll update the committer guide and
>  GitHub PR
> >> template with the new language, and check the CI/CD for GitHub
> >> Actions
>  too.
> >> Thanks. br/> <
> >> br/>>> Andy LooPresto
> >> alopre...@apache.org
> >> alopresto.apa...@gmail.com
> >> He/Him
> >> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3

Re: Developer Guide - Where to start ?

[Peter Turcsanyi]

Hi Abdou,

You can easily filter the issues by Label.

I also found this saved filter by Aldrin Piri that can be used:
NiFi Unassigned Issues Tagged Beginner
https://issues.apache.org/jira/issues/?filter=12333139

Regards,
Peter

On Sun, Jun 7, 2020 at 7:34 PM Abdou B  wrote:

> Hello,
> I was reading the developer guide on Where to Start.
> When I go the JIRA Page.
> I don't find any filter where on beginner.
> Do I miss something?
>
> Best Regards
> Abdou
>

Re: [ANNOUNCE] New NiFi PMC member Drew Lim

[Peter Turcsanyi]

Congrats Drew!

On Fri, May 29, 2020 at 10:50 PM Joe Witt  wrote:

> congrats Drew!  youve been helping make nifi easier to use for a long time
>
> On Fri, May 29, 2020 at 1:32 PM Andy LoPresto 
> wrote:
>
> > Congratulations and welcome Drew. The work you’ve done makes the
> community
> > so much more accessible and drives user success everywhere. I refer to
> your
> > work myself all the time. Looking forward for your continued
> contributions.
> >
> > Andy LoPresto
> > alopre...@apache.org
> > alopresto.apa...@gmail.com
> > He/Him
> > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
> >
> > > On May 29, 2020, at 1:18 PM, Pierre Villard <
> pierre.villard...@gmail.com>
> > wrote:
> > >
> > > Awesome Drew! Congrats! Your work is super useful for all the
> community,
> > > well deserved!
> > >
> > > Le ven. 29 mai 2020 à 21:55, Tony Kurc  a écrit :
> > >
> > >> NiFi Community,
> > >>
> > >> On behalf of the Apache NiFi PMC, I am pleased to announce that Drew
> Lim
> > >> has accepted the PMC's invitation to join the Apache NiFi PMC.
> > >>
> > >> Drew has been doing an amazing job for several years making NiFi more
> > >> approachable and usable. He's contributed to almost every part of
> NiFi;
> > >> going over and beyond to improve documentation and usability.
> > >>
> > >> Please join us in congratulating and welcoming Drew to the Apache NiFi
> > PMC.
> > >>
> > >> Congratulations Drew!
> > >>
> > >> Tony
> > >>
> >
> >
>

Re: [ANNOUNCE] New NiFi PMC member Arpad Boda

[Peter Turcsanyi]

Congrats Arpad!

On Fri, May 29, 2020 at 10:46 PM Joe Witt  wrote:

> Congrats and thank you!
>
> On Fri, May 29, 2020 at 1:32 PM Andy LoPresto 
> wrote:
>
> > Congratulations Arpad, very well deserved and excited to see your
> > continued contributions. Pálinka on me next time I’m in Budapest.
> >
> > Andy LoPresto
> > alopre...@apache.org
> > alopresto.apa...@gmail.com
> > He/Him
> > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
> >
> > > On May 29, 2020, at 1:16 PM, Pierre Villard <
> pierre.villard...@gmail.com>
> > wrote:
> > >
> > > Congrats Arpad, very well deserved!
> > >
> > > Le ven. 29 mai 2020 à 21:48, Tony Kurc  a écrit :
> > >
> > >> NiFi Community,
> > >>
> > >> On behalf of the Apache NiFi PMC, I am pleased to announce that Arpad
> > Boda
> > >> has accepted the PMC's invitation to join the Apache NiFi PMC.
> > >>
> > >> In addition to being a regular code contributor and engaged community
> > >> member with the project, (especially MiNiFi C++!) for quite some time,
> > >> Arpad has done the arduous task of being a release manager for both
> NiFi
> > >> Registry and MiNiFi C++, which is a challenging and detail oriented
> > task.
> > >>
> > >> Please join us in congratulating and welcoming Arpad to the Apache
> NiFi
> > >> PMC.
> > >>
> > >> Congratulations Arpad!
> > >>
> > >> Tony
> > >>
> >
> >
>

Re: Nifi context path

[Peter Turcsanyi]

Hi Ganesh,

Please subscribe to the mailing list in order to get the replies:
http://nifi.apache.org/mailing_lists.html
You can find the archived mails there too.

Regards,
Peter

On Wed, May 27, 2020 at 6:32 AM Ganesh, B (Nokia - IN/Bangalore) <
b.gan...@nokia.com> wrote:

> Hi ,
>
> Can anyone respond please ?
>
> Thanks & Regards,
> Ganesh.B
>
> From: Ganesh, B (Nokia - IN/Bangalore)
> Sent: Tuesday, May 26, 2020 10:18 AM
> To: 'dev@nifi.apache.org' 
> Subject: Nifi context path
>
> Hi ,
>
> I am accessing  the nifi UI  with http://localhost:8080/nifi in my VM or
> windows machine .
>
> I want to configure Nifi to access with our own context path i.e
> http://localhost:8080/
>
> I tried configuring the nifi properties like below .
> nifi.web.proxy.context.path="/ "
> nifi.web.proxy.host=localhost:8080
>
> For one of the requirement we need to change the config path form "/nifi"
> to "/" to access nifi with " http://localhost:8080/ " could  anyone help
> me to do the same or the possibility to do .
>
> Thanks & Regards,
> Ganesh.B
>
>
>

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

[Peter Turcsanyi]

+1 (non-binding)

Verified signature/hashes.
Built from source successfully.
Checked the binary release on Java 8 and 11, running some flows including
PutHDFS using native libs.

On Wed, Jan 22, 2020 at 8:19 PM Muazma Zahid  wrote:

> +1 (binding)
> Deployed and tested 10 node Cluster in Azure with the standard flow and
> high throughput along with the latest changes in the Azure Reporting task.
>
> On Wed, Jan 22, 2020 at 11:03 AM Nathan Gough  wrote:
>
> > +1 non-binding
> >
> > Verified hashes, signing key, did a 'mvn clean install
> > -Pcontrib-check,include-grpc' and ran a secured NiFi cluster with the
> > resulting bin.
> >
> > Nathan
> >
> > On Wed, Jan 22, 2020 at 11:51 AM Shawn Weeks 
> > wrote:
> >
> > > +1 non-binding
> > >
> > > On 1/22/20, 10:48 AM, "Shawn Weeks" 
> wrote:
> > >
> > > Noticed that the docker compose file
> > > nifi-docker/docker-compose/docker-compose.yml still references
> > > 1.10.0-SNAPSHOT-dockermaven in RC3. Not worth holding up for though.
> > >
> > > Thanks
> > > Shawn
> > >
> > > On 1/22/20, 9:55 AM, "Kevin Doran"  wrote:
> > >
> > > +1 (binding)
> > >
> > > I followed the steps in the release helper guide and verified
> the
> > > signs, hashes, readme, license, etc.
> > > I was able to performa fun build with tests without any issues
> on
> > > macOS 10.15 (Catalina).
> > > The resulting binary runs well for me running a standard suite
> of
> > > test flows.
> > >
> > > One issue I ran into was building the Docker image (via
> > > dockermaven) from the release source code using the -Pdocker profile. I
> > was
> > > unable to build a usable docker image from the source code due to
> > > assumptions the Dockerfile makes about the permissions of some shell
> > > scripts. It appears at some point the file permissions for the shell
> > > scripts included in this release were changed and are no longer
> > executable.
> > > Not a huge deal so long as we can still build a Dockerhub image for
> this
> > > release once finalized, but just something to note as perhaps we could
> > > improve our automated image creation process to be more robust.
> > >
> > > Thanks for everyone who has worked on the improvements landing
> in
> > > this release and thanks to Joe for RM’ing again!
> > >
> > > Kevin
> > >
> > > > On Jan 21, 2020, at 16:43, Andrew Lim <
> > > andrewlim.apa...@gmail.com> wrote:
> > > >
> > > > +1 (non-binding)
> > > >
> > > > -Ran full clean install on OS X (Catalina 10.15.2)
> > > > -Tested secure NiFi with secure NiFi Registry
> > > > -Ran basic flows successfully
> > > > -Reviewed core UI and documentation fixes/updates
> > > >
> > > > In setting up my secure NiFi and secure NiFi registry, I used
> > > the NiFi TLS Toolkit [1] to create my config files and certs. I was
> able
> > to
> > > access the UIs of both apps using Safari but not able to with Chrome
> due
> > to
> > > a NET::ERR_CERT_REVOKED error which I had never seen before.  Turns out
> > > this is a known issue on Catalina [2]. MacOSX 10.15 requires certs to
> be
> > > valid for 825 days or less and a minimum 2048 bit key.  By default, the
> > TLS
> > > Toolkit sets the validity to 1095 days and the number of bits for
> > generated
> > > keys to 2048. Creating new certs with the required 825 validity solved
> > the
> > > issue. I will add a note to the Toolkit Guide for this new requirement
> > [3].
> > > >
> > > > Drew
> > > >
> > > > [1]
> > >
> >
> https://nifi.apache.org/docs/nifi-docs/html/toolkit-guide.html#tls_toolkit
> > > <
> > >
> >
> https://nifi.apache.org/docs/nifi-docs/html/toolkit-guide.html#tls_toolkit
> > > >
> > > > [2] https://support.apple.com/en-us/HT210176 <
> > > https://support.apple.com/en-us/HT210176>
> > > > [3] https://issues.apache.org/jira/browse/NIFI-7053 <
> > > https://issues.apache.org/jira/browse/NIFI-7053>
> > > >
> > > >
> > > >> On Jan 19, 2020, at 3:21 PM, Joe Witt 
> > > wrote:
> > > >>
> > > >> Hello,
> > > >>
> > > >> I am pleased to be calling this vote for the source release
> of
> > > Apache NiFi
> > > >> nifi-1.11.0.
> > > >>
> > > >> The source zip, including signatures, digests, etc. can be
> > > found at:
> > > >>
> > > https://repository.apache.org/content/repositories/orgapachenifi-1155
> > > >>
> > > >> The source being voted upon and the convenience binaries can
> > be
> > > found at:
> > > >> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.11.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-

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

[Peter Turcsanyi]

+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
> > > pulled
> > > > > into
> > > > > > > RC3 are working as expected.
> > > > > > >
> > > > > > > Shayne
> > > > > > >
> > > > > > > On Wed, Oct 30, 2019 at 5:59 PM Jeff Zemerick <
> > > jzemer...@apache.org>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > +1 (non-binding)
> > > > > > > >
> > > > > > > > Built and ran successfully and built custom processor with
> 1.10.0
> > > > > > > > dependency and successfully uploaded NAR to NiFi Registry
> 0.5.0.
> > > > > > > >
> > > > > > > > On Wed, Oct 30, 2019 at 4:06 PM Mark Payne <
>

Re: [ANNOUNCE] New Apache NiFi Committer Peter Turcsanyi

[Peter Turcsanyi]

Thank you everyone!

Peter

On Mon, Oct 28, 2019 at 6:06 PM Andy LoPresto  wrote:

> Congratulations Peter. Looking forward to your continued contributions.
>
> Andy LoPresto
> alopre...@apache.org
> alopresto.apa...@gmail.com
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
>
> > On Oct 28, 2019, at 9:39 AM, Matt Burgess  wrote:
> >
> > Congratulations Peter!
> >
> > On Sun, Oct 27, 2019 at 9:05 PM Aldrin Piri 
> wrote:
> >>
> >> Apache NiFi community,
> >>
> >> On behalf of the Apache NiFI PMC, I am very pleased to announce that
> Peter
> >> has accepted the PMC's invitation to become a committer on the Apache
> NiFi
> >> project. We greatly appreciate all of Peter's hard work and generous
> >> contributions to the project. We look forward to continued involvement
> >> in the project.
> >>
> >> Peter has provided several new extensions and improvements enhancing
> NiFi's
> >> interoperability with cloud services.  He has also found and remedied
> >> several bugs, is a regular participant in code reviews and an active
> >> presence on the mailing lists helping out the community.
> >>
> >> Welcome and congratulations!
>
>

Re: convert json to csv on nifi

[Peter Turcsanyi]

Hi Anushke,

What is the json path you would like to evaluate?

The only array (that could be the target of SplitJson) is inside "details".
"details" is of type string which contains escaped json content so it won't
be parsed. Is the escaping intentional?

Kind regards,
Peter

On Sun, Aug 25, 2019 at 9:44 PM Anushka Hewawitharana 
wrote:

> Dear Team,
>
> I have listen json kafka feed and put to flat files using nifi
> Now i need to convert them to csv using nifi.
>
>
>
> But i have error on "json path"  attribute on splitjson processor.
> My sample json as below.
>
>{
>   "section":"prepaid_myplan",
>   "action":"change_mypaln",
>   "sender":null,
>   "recipient":null,
>
> "details":"{\"channel\":\"SCAPP\",\"planId\":\"1\",\"serviceAmounts\":[{\"serviceId\":\"5\",\"usageAmount\":\"0\"},{\"serviceId\":\"4\",\"usageAmount\":\"0\"},{\"serviceId\":\"1\",\"usageAmount\":\"0\"},{\"serviceId\":\"2\",\"usageAmount\":\"50\"}],\"totalValue\":\"137700\"}",
>   "amount":null,
>   "account_no":null,
>   "datetime":"2011-08-20 11:18:38",
>   "msisdn":"5",
>   "imei":"null",
>   "nic":"15504555",
>   "lob":"MOBILE",
>   "deviceOs":"android",
>   "appVersion":"9.0.0",
>   "deviceModelId":"MSM55574",
>   "connType":"PREPAID",
>   "language":"en",
>   "device_id":null,
>   "status":"SUCCESS"
>}
>
> kindly advise me on json path for above
>
>
>
> Regards
> Anushke
>
>
>
>
>

Re: How to decrypt one field in a Json and return the original JSON with that field decrypted

[Peter Turcsanyi]

Hi JP,

If I understand correctly, your scenario would be:
1. extract the encrypted data item from json (into a flowfile attribute)
2. decrypt the data
3. replace the encrypted data item with the decrypted one in json

Unfortunately, there is no EncryptAttribute processor at the moment which
would be more suitable for this scenario (though there is an open issue
 for it).

You can do it with EncryptContent too but it is a bit complicated because
you need to put the encrypted data into the flowfile content and decrypt it
there.

A possible scenario:
- back up the original json into an attribute** with ExtractText
- extract the encrypted data item from the json into an attribute with
EvaluateJsonPath
- replace the whole flowfile content to the encrypted data with ReplaceText
- base64 decode the encrypted data in the flowfile content with
Base64EncodeContent (I supposed your json contains the password as base64
encoded string)
- decrypt the flowfile content with EncryptContent
- copy the decrypted password from the content into an attribute with
ExtractText
- restore the original json into the content (from the attribute where it
was saved) with ReplaceText
- replace the encrypted data item with the decrypted one in the json with
ReplaceText

**The drawback is (beyond the complexity) that the flowfile content (the
original json) needs to be stored in an attribute which is not really
recommended (or only in case of small files).

It could be avoided by splitting the flow into 2 branches, one for the
original json (in the conient, not in an attribute) and one for the data
decryption, then merge the two branches with MergeContent. However, it
would be more complicated than the previous one because you need to handle
the merging of the two branches.

If there won't be better suggestions to solve your scenario, I can share
the sample flow I described above.


Regards,
Peter

On Tue, Apr 16, 2019 at 1:34 AM jpconver  wrote:

> Dear all!
>
> I'm a Nifi Newbie and I'd like some guidance to solve this problem.
>
> I have a use case where I receive a JSON with one field encrypted. What I'd
> like to do is to process this JSON with NiFi and return the original JSON
> but with the field decrypted. I'd like to use the processor EncryptContent
> if that's possible.
> I know the name of the encrypted field in advance.
>
> For example if a Receive the following json
>
> {"id":"1","name":"paul","password":"encryptedPassword"}
>
> I'd like to return (or have an some point of the flow)
>
> {"id":"1","name":"paul","password":"decryptedPassword"}
>
> What would be the best strategy to achieve this without developing a custom
> processor?
>
> Thanks!
>   JP
>
>
>
>
>
>
>
>
>
> --
> Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/
>

Re: Execute SQL support for nvarchar(max) datatype

[Peter Turcsanyi]

Hi Venu,

If I'm not wrong, you're using MS SQL Server and nvarchar / varbinary are
the database column types.
nvarchar can be used for storing character data (strings) but it is not
suitable for binary data (like pdf).

I think NiFi tries to handle the bytes of the pdf file as Unicode
characters. It could be debugged but my short answer is that nvarchar
should not be used for binary data.

Regards,
Peter

On Mon, Apr 15, 2019 at 10:05 PM Venugopal Iyengar 
wrote:

> Hello there,
> I am using Execute SQL, Split AVro and put file processors to read some
> pdf documents stored in SQL database and store that in the file system.
>
> When I use varbinary(max)  I was able to pull and view the pdf without any
> issues.
>
> When the datatype is nvarchar(max) I am unable to open the pdf file.
>
> I appreciate if some body can shed some light on this. How can I debug
> this?
>
> Thanks
> Venu
>
>
> [image: image.png]
>

Re: Get files using ListFile but filtering by its name that has a date inside it

[Peter Turcsanyi]

Hi,

File Filter property of ListFile does not support expression language so I
am afraid you will not be able to use the now() function there.

As an alternative solution, you can use ListFile without filtering and add
RouteOnAttribute after ListFile with the following match condition against
the filename:
${filename:matches(${now():format("'TRB_[A-Z]{3}_D'yyMMdd'\.TXT'")})}

There might exist a more elegant solution though...

Best,
Peter

On Thu, Mar 21, 2019 at 8:28 PM mtigua  wrote:

> Hello everyone, please help!
>
> I have files whose name is formed by a date in the format "yymmdd", for
> example:
>
> TRB_ASE_D190125.txt
>
> TRB_TIT_D190125.txt
>
> I need to get only the files whose names match the current date. For
> example, if the date was "190125", the 2 subsequent files would match that
> criterion.
>
> I am using the ListFile processor to get the files and put this regular
> expression using the "now" function in the File Filter, but it does not
> work:
>
> ^TRB_[A-Z]+_D${now():format('yymmdd')}.TXT
>
>
>
> Thanks in advance!
>
>
>
> --
> Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/
>

Re: How to remove a specific pattern from the flow file through replace text in nifi by using regex

[Peter Turcsanyi]

Hi,

You can use ReplaceText with the following config:
Search Value: (?s)(^.*=TEXT)
Replacement Value: [Empty string]

Best,
Peter

On Thu, Mar 21, 2019 at 11:54 AM Puspak  wrote:

> Hi i am relatively new to nifi and expression language .Please help
>
> Sample flow file :
>
> =HEADER
> RCV,2019/02/27 08:34
> =PRIORITY
> QK
> 270834
> =SMI
> FFD
> =TEXT
> FFD/8
> 1/BY0077/27FEB1045/CMB/GB/27FEB1200/LGW
> ULD/PMC74349R7
> 612-56018325CMBLHR/T130K1172.50MC10.08/CONSOL
> /DHC
> LAST
>
> The desired flow file after replacement is :
> FFD/8
> 1/BY0077/27FEB1045/CMB/GB/27FEB1200/LGW
> ULD/PMC74349R7
> 612-56018325CMBLHR/T130K1172.50MC10.08/CONSOL
> /DHC
> LAST
>
> basically i just want to trim-out the below portion from the flow file.
>
> =HEADER
> RCV,2019/02/27 08:34
> =PRIORITY
> QK
> 270834
> =SMI
> FFD
> =TEXT
>
>
>
> --
> Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/
>