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

[Andrew Lim]

+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:
> 5f6da64e75a2d5446f1f274fe3de7e97290f5b916eabbc0491a99c6db33f74fbdea001b403044e75bc5c2183fb0500dfc143d0f4cba19d3511f866fff774d7f5
> 
> 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
> 
> 186 issues were closed/resolved for this release:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12353069
> 
> Release note highlights can be found here:
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.22.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.22.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...

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

[Emilio Setiadarma]

+1 (non-binding)

Verified signature and SHA256/512 hashes of the release.
OS: MacOS Monterey 12.6.5
Java version: OpenJDK version 11.0.18
Ran the build, and booted up NiFi with no issues, was able to start up a
simple flow

On Thu, Jun 8, 2023 at 12:25 PM David Handermann <
exceptionfact...@apache.org> wrote:

> +1 (binding)
>
> - Verified signatures and hashes
> - Ran build using Maven 3.9.2
> - Ran build on macOS 13.4 with Azul Zulu JDK 1.8.0-372 AArch64
> - Ran build on Ubuntu 22.04 with Azul Zulu JDK 1.8.0-372 x86_64
> - Ran build on Ubuntu 22.04 with Azul Zulu JDK 11.0.19 x86_64
> - Ran build on Ubuntu 22.04 with Azul Zulu JDK 17.0.7 x86_64
> - Ran stateless and system tests on macOS 13.4 with Azul Zulu JDK 1.8.0-372
> AArch64
> - Ran stateless and system tests on Ubuntu 22.04 with Azul Zulu JDK 17.0.7
> x86_64
>
> - Ran NiFi on macOS 13.4 with Azul Zulu JDK 1.8.0-372 AArch64
> - Ran NiFi on macOS 13.4 with Azul Zulu JDK 11.0.16 x86_64
> - Ran NiFi Toolkit Encrypt Config command with AES-GCM
> - Configured OpenID Connect authentication with Okta
> - Configured OpenID Connect authentication with Keycloak 21
> - Configured reverse proxy with HTTPS and forwarded context path
> - Configured cluster with external ZooKeeper and multiple NiFi nodes
>
> - Ran NiFi Registry on Ubuntu 22.04 with Azul Zulu JDK 11.0.18 x86_64
> - Created Buckets
> - Verified Flow Version Control
>
> - NIFI-2964 Verified AttributesToJSON default Escaped strategy and
> configurable Nested strategy
> - NIFI-11222 Verified deprecation log for Processor MongoDB URI Property
> - NIFI-11385 Verified default access and filtering for JMX Metrics through
> the REST API
> - NIFI-11438 Verified OIDC configuration sends minimum required scopes
> - NIFI-11461 Verified Tenant User and Group Search when adding Policies
> - NIFI-11466 Verified ModifyCompression Processor with several compression
> strategies
> - NIFI-11509 Verified ValidateJson allows comments in JSON FlowFiles
> - NIFI-11511 Verified Provenance ROUTE events for ValidationJson
> - NIFI-11547 Verified DBCPConnectionPool verification works as expected
> - NIFI-11558 Verified Security Headers applied to Registry HTTP responses
> - NIFI-11614 Verified JndiJmsConnectionFactoryProvider and JMS Processors
> URL validation
> - NIFI-11630 Verified ECMAScript Script Engine marked as deprecated
> - NIFI-11644 Verified Hazelcast 5.3.0 Embedded Server
> - NIFI-11646 Verified Lua and Ruby Script Engines marked as deprecated
> - NIFI-11651 Verified InvokeHTTP with HTTP/2 using OkHttp 4.11.0
> - NIFI-11653 Verified DBCPConnectionPool and HikariCPConnectionPool reject
> H2 URL
>
> I noticed that the commit for NIFI-11629 adding the Socket Write Timeout
> property to InvokeHTTP was not backported, but as a new property, this is
> not a blocker. I backported the commit and set the Fix Version to 1.23.0.
>
> As Matthew Kiprop mentioned, I noticed that ModifyCompression did not
> include the exception stack trace when logging errors. This also is not a
> blocker. I filed NIFI-11666 and created a pull request to correct the
> behavior for future releases.
>
> Thanks Joe!
>
> Regards,
> David Handermann
>
> On Tue, Jun 6, 2023 at 4: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:
> >
> >
> 5f6da64e75a2d5446f1f274fe3de7e97290f5b916eabbc0491a99c6db33f74fbdea001b403044e75bc5c2183fb0500dfc143d0f4cba19d3511f866fff774d7f5
> >
> > 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
> >
> > 186 issues were closed/resolved for this release:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12353069
> >
> > Release note highlights can be found here:
> >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.22.0
> >
> > The vote will be open for 72 hours.
> > Please download the release c

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

[David Handermann]

+1 (binding)

- Verified signatures and hashes
- Ran build using Maven 3.9.2
- Ran build on macOS 13.4 with Azul Zulu JDK 1.8.0-372 AArch64
- Ran build on Ubuntu 22.04 with Azul Zulu JDK 1.8.0-372 x86_64
- Ran build on Ubuntu 22.04 with Azul Zulu JDK 11.0.19 x86_64
- Ran build on Ubuntu 22.04 with Azul Zulu JDK 17.0.7 x86_64
- Ran stateless and system tests on macOS 13.4 with Azul Zulu JDK 1.8.0-372
AArch64
- Ran stateless and system tests on Ubuntu 22.04 with Azul Zulu JDK 17.0.7
x86_64

- Ran NiFi on macOS 13.4 with Azul Zulu JDK 1.8.0-372 AArch64
- Ran NiFi on macOS 13.4 with Azul Zulu JDK 11.0.16 x86_64
- Ran NiFi Toolkit Encrypt Config command with AES-GCM
- Configured OpenID Connect authentication with Okta
- Configured OpenID Connect authentication with Keycloak 21
- Configured reverse proxy with HTTPS and forwarded context path
- Configured cluster with external ZooKeeper and multiple NiFi nodes

- Ran NiFi Registry on Ubuntu 22.04 with Azul Zulu JDK 11.0.18 x86_64
- Created Buckets
- Verified Flow Version Control

- NIFI-2964 Verified AttributesToJSON default Escaped strategy and
configurable Nested strategy
- NIFI-11222 Verified deprecation log for Processor MongoDB URI Property
- NIFI-11385 Verified default access and filtering for JMX Metrics through
the REST API
- NIFI-11438 Verified OIDC configuration sends minimum required scopes
- NIFI-11461 Verified Tenant User and Group Search when adding Policies
- NIFI-11466 Verified ModifyCompression Processor with several compression
strategies
- NIFI-11509 Verified ValidateJson allows comments in JSON FlowFiles
- NIFI-11511 Verified Provenance ROUTE events for ValidationJson
- NIFI-11547 Verified DBCPConnectionPool verification works as expected
- NIFI-11558 Verified Security Headers applied to Registry HTTP responses
- NIFI-11614 Verified JndiJmsConnectionFactoryProvider and JMS Processors
URL validation
- NIFI-11630 Verified ECMAScript Script Engine marked as deprecated
- NIFI-11644 Verified Hazelcast 5.3.0 Embedded Server
- NIFI-11646 Verified Lua and Ruby Script Engines marked as deprecated
- NIFI-11651 Verified InvokeHTTP with HTTP/2 using OkHttp 4.11.0
- NIFI-11653 Verified DBCPConnectionPool and HikariCPConnectionPool reject
H2 URL

I noticed that the commit for NIFI-11629 adding the Socket Write Timeout
property to InvokeHTTP was not backported, but as a new property, this is
not a blocker. I backported the commit and set the Fix Version to 1.23.0.

As Matthew Kiprop mentioned, I noticed that ModifyCompression did not
include the exception stack trace when logging errors. This also is not a
blocker. I filed NIFI-11666 and created a pull request to correct the
behavior for future releases.

Thanks Joe!

Regards,
David Handermann

On Tue, Jun 6, 2023 at 4: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:
>
> 5f6da64e75a2d5446f1f274fe3de7e97290f5b916eabbc0491a99c6db33f74fbdea001b403044e75bc5c2183fb0500dfc143d0f4cba19d3511f866fff774d7f5
>
> 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
>
> 186 issues were closed/resolved for this release:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12353069
>
> Release note highlights can be found here:
>
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.22.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.22.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>

Stopping NiFi service in windows

[Ivan Dolinin]

Hello,

I realize that running NiFi as a service in Windows is not supported, but it 
worked in 1.8. We upgraded to 1.20. We use procrun to run NiFi as a service. 
When we stop the service, a thread running NiFi remains running. Is there a way 
to properly handle shutting it down?

[cid:image001.png@01D99A14.B0E8A3C0]

Thanks,


Ivan Dolinin
Principal Software Developer
Clever Devices
Transit Matters Here.
Office:  (416) 583-5833 x2012
idoli...@cleverdevices.com
www.cleverdevices.com

Re: Possible Docker bug in 1.13.2

[Mathew Kiprop]

Russel,

I faced a similar issue recently and reported on slack channel.
I am working on a fix and hopefully submit a PR in the coming hours.
Chris was resourceful pointing out the cause.

Thanks,
Mathew

On Thu, 8 Jun 2023 at 15:58, Russell Bateman  wrote:

> Thanks, Chris.
>
> In fact, I merely hand-corrected the instances of the version in
> /Dockerfile/ and in /DockerImage.txt/, then ran /DockerBuild.sh/. I got
> exactly the image I wanted. It looked like a potential if irrelevant bug
> and I thought I'd report it.
>
> Best,
> Russ
>
> On 6/7/23 19:17, Chris Sampson wrote:
> > The DockerImage.txt file isn't always updated in the repo, a bit like the
> > README for Docker Hub - it probably should be, but is often forgotten
> (same
> > for all of the convenience images built after a release). Indeed, this is
> > currently set to 1.15.1 on `main`, but the images in Docker Hub since
> then
> > have certainly not used an incorrect version.
> >
> > Nifi 1.16.0 [1] updated the DockerBuild.sh script to allow easier
> > specification of the NIFI_IMAGE_VERSION from the command line. A small
> > issue has just been spotted with this script's use of the text file to
> > obtain the version's default value too [4].
> >
> > Before then, I think the process was for someone (with access to push
> > images to Docker Hub) to change the text file locally, build & push the
> > image, but not always then raise a PR to update the text file.
> >
> > To manually build the Docker Image locally containing the correct version
> > of the downloaded convenience binary from the Apache servers, simply
> > recreate the `docker build` command from within the DockerBuild.sh [2]
> > file, substituting the correct values for the `--build-arg`s.
> >
> > Alternatively, run the dockermaven [3] build for the repo (having checked
> > out the correct tag from GitHub), enabling the `-P docker` profile as you
> > do so in your `mvn` command. Note, however, that there were differences
> > between the dockermaven and dockerhub builds (both the included script
> > files and the Dockerfile structure) that weren't rationalised until NiFi
> > 1.16.0+.
> >
> >
> > [1]:
> >
> https://github.com/apache/nifi/blob/rel/nifi-1.16.0/nifi-docker/dockerhub/DockerBuild.sh
> >
> > [2]:
> >
> https://github.com/apache/nifi/blob/rel/nifi-1.13.2/nifi-docker/dockerhub/DockerBuild.sh#L36
> >
> > [3]:
> >
> https://github.com/apache/nifi/tree/rel/nifi-1.16.0/nifi-docker/dockermaven
> >
> > [4]:
> >
> https://apachenifi.slack.com/archives/CDGMCSDJT/p1686135561932289?thread_ts=1686135561.932289&cid=CDGMCSDJT
> >
> > On Thu, 8 Jun 2023, 00:10 Russell Bateman,
> wrote:
> >
> >> I'm re-rolling in order to update the Java inside to 11 in order to
> >> permit using the new Java HTTP client. This seems to work well; I fixed
> >> the bug locally.
> >>
> >> Maybe too old to be important, but NiFi 1.14.0 is a quantum step up for
> >> several aspects of processor writing requiring refactoring. So, until we
> >> can shed the old NAR we cannot rebuild, we're stuck at NiFi 1.13.2.
> >>
> >>
> >> On 6/7/23 15:31, Russell Bateman wrote:
> >>> I downloaded sources to 1.13.2 in order to hand-spin my own container
> >>> image. When I got down to
> >>> /nifi-1.13.2/nifi-docker/dockerhub/Dockerfile/, I found:
> >>>
> >>>  ...
> >>>  ARG NIFI_VERSION=1.13.1
> >>>  ...
> >>>
> >>> and the version is also wrong in /DockerImage.txt/ which
> >>> /DockerBuild.sh/ consumes.
> >>>
> >>> Indeed, the image that is built appears to be versioned 1.13.1 and not
> >>> 1.13.2 when listing local Docker repository images:
> >>>
> >>>  *REPOSITORY TAG IMAGE ID   CREATED  SIZE*
> >>>  apache/nifi 1.13.1  8c18038f152a   30 minutes ago 2.06GB
> >>>
> >>> Why am I juggling so ancient a version? Because I have custom
> >>> processors that cannot be rebuilt (source-code gone) and will not run
> >>> on 1.14.0 and later.
> >>>
> >>> Russ
>

Re: Possible Docker bug in 1.13.2

[Russell Bateman]

Thanks, Chris.

In fact, I merely hand-corrected the instances of the version in 
/Dockerfile/ and in /DockerImage.txt/, then ran /DockerBuild.sh/. I got 
exactly the image I wanted. It looked like a potential if irrelevant bug 
and I thought I'd report it.


Best,
Russ

On 6/7/23 19:17, Chris Sampson wrote:

The DockerImage.txt file isn't always updated in the repo, a bit like the
README for Docker Hub - it probably should be, but is often forgotten (same
for all of the convenience images built after a release). Indeed, this is
currently set to 1.15.1 on `main`, but the images in Docker Hub since then
have certainly not used an incorrect version.

Nifi 1.16.0 [1] updated the DockerBuild.sh script to allow easier
specification of the NIFI_IMAGE_VERSION from the command line. A small
issue has just been spotted with this script's use of the text file to
obtain the version's default value too [4].

Before then, I think the process was for someone (with access to push
images to Docker Hub) to change the text file locally, build & push the
image, but not always then raise a PR to update the text file.

To manually build the Docker Image locally containing the correct version
of the downloaded convenience binary from the Apache servers, simply
recreate the `docker build` command from within the DockerBuild.sh [2]
file, substituting the correct values for the `--build-arg`s.

Alternatively, run the dockermaven [3] build for the repo (having checked
out the correct tag from GitHub), enabling the `-P docker` profile as you
do so in your `mvn` command. Note, however, that there were differences
between the dockermaven and dockerhub builds (both the included script
files and the Dockerfile structure) that weren't rationalised until NiFi
1.16.0+.


[1]:
https://github.com/apache/nifi/blob/rel/nifi-1.16.0/nifi-docker/dockerhub/DockerBuild.sh

[2]:
https://github.com/apache/nifi/blob/rel/nifi-1.13.2/nifi-docker/dockerhub/DockerBuild.sh#L36

[3]:
https://github.com/apache/nifi/tree/rel/nifi-1.16.0/nifi-docker/dockermaven

[4]:
https://apachenifi.slack.com/archives/CDGMCSDJT/p1686135561932289?thread_ts=1686135561.932289&cid=CDGMCSDJT

On Thu, 8 Jun 2023, 00:10 Russell Bateman,  wrote:


I'm re-rolling in order to update the Java inside to 11 in order to
permit using the new Java HTTP client. This seems to work well; I fixed
the bug locally.

Maybe too old to be important, but NiFi 1.14.0 is a quantum step up for
several aspects of processor writing requiring refactoring. So, until we
can shed the old NAR we cannot rebuild, we're stuck at NiFi 1.13.2.


On 6/7/23 15:31, Russell Bateman wrote:

I downloaded sources to 1.13.2 in order to hand-spin my own container
image. When I got down to
/nifi-1.13.2/nifi-docker/dockerhub/Dockerfile/, I found:

 ...
 ARG NIFI_VERSION=1.13.1
 ...

and the version is also wrong in /DockerImage.txt/ which
/DockerBuild.sh/ consumes.

Indeed, the image that is built appears to be versioned 1.13.1 and not
1.13.2 when listing local Docker repository images:

 *REPOSITORY TAG IMAGE ID   CREATED  SIZE*
 apache/nifi 1.13.1  8c18038f152a   30 minutes ago 2.06GB

Why am I juggling so ancient a version? Because I have custom
processors that cannot be rebuilt (source-code gone) and will not run
on 1.14.0 and later.

Russ

Re: [Sender Not Verified] Re: Issue upgrading Nifi(1.7.0) & Minifi(0.5.0) to 1.20.0

[Comas, Joan]

Dear Matt,

I am taking over the Architecture role from Ignasi.

Would it be possible for you to check Francisco's latest comments and come
back with some feedback?

We would really appreciate it,

Thanks a lot and kind regards

On Wed, May 3, 2023 at 10:55 AM Nery, Francisco <
francisco.n...@contractors.roche.com> wrote:

> Hello Matt,
>
> Our custom nars have already been recompiled and rebuilt with the version
> 1.20.0. Any other ideas? Or any other info you need? We have not tried with
> the latest 1.21.0 version although I don't think the problem would be
> solved.
>
> Regards,
> Francisco.
>
> On Sat, Apr 29, 2023 at 4:38 PM Matt Burgess  wrote:
>
>> Ignasi,
>>
>> A lot has changed between MiNiFi 0.5.0 and MiNiFi 1.20.0, including
>> changes to NARs, how they are loaded, etc. For custom NARs I would try to
>> rebuild them using the same version of NiFi and MiNiFi dependencies. The
>> latest Apache NiFi release is now 1.21.0 so I would change the NiFi and
>> MiNiFi dependencies in your custom NARs to 1.21.0. You may find that there
>> are compilation errors or some issue that wasn't there before, these would
>> be things introduced between NiFi 1.7.0 and NiFi 1.21.0. I can't think of
>> any offhand but wanted to mention it in case your NARs no longer
>> compile/build.
>>
>> Regards,
>> Matt
>>
>>
>> On Fri, Apr 28, 2023 at 5:31 AM Garriga, Ignasi
>>  wrote:
>>
>>> Hi all,
>>>
>>> We're trying to upgrade versions of Apache Nifi 1.7.0 with Minifi 0.5.0
>>> to the latest embedded version 1.20.0.
>>> We have some custom nars that when we add to the project there are
>>> problems with the Classloader and bundle not found:
>>>
>>> ERROR [main] o.a.n.n.StandardExtensionDiscoveringManager Could not
>>> instantiate class of type 
>>> org.apache.nifi.processors.standard.JoltTransformJSON
>>> using ClassLoader for bundle default:unknown:unversioned because the bundle
>>> could not be found
>>>
>>>
>>> In the following pictures I share with you the docker-compose that we
>>> use to create an image and all libraries that we use to compile. It can
>>> help to identify something or give a clue to find the solution.
>>>
>>> pm-data-pipeline:
>>> image: apache/nifi-minifi:1.20.0
>>> restart: always
>>> hostname: pm-data-pipeline
>>> container_name: pm-data-pipeline
>>> environment:
>>>   - NIFI_WEB_HTTPS_PORT=9443
>>> ports:
>>>   - "8080:8080"
>>>   - "9443:9443"
>>> volumes:
>>>   - 
>>> ../../../assets/templates/nMonFlow.yml:/opt/minifi/minifi-1.20.0/conf/config.yml
>>>   - 
>>> ../../../assets/nifi-invoke-igw-nar-1.6.0.nar:/opt/minifi/minifi-1.20.0/lib/nifi-invoke-igw-nar-1.6.0.nar
>>>   - 
>>> ../../../assets/pm-data-pipeline-ssl-context-service-nar-1.0.0.nar:/opt/minifi/minifi-1.20.0/lib/pm-data-pipeline-ssl-context-service-nar-1.0.0.nar
>>>   - 
>>> ../../../assets/nifi-amqp-nar-1.20.0.nar:/opt/minifi/minifi-1.20.0/lib/nifi-amqp-nar-1.20.0.nar
>>>
>>>
>>> [image: image.png]
>>>
>>>
>>> Thank you in advance for your support and don't hesitate to contact us
>>> if you need more information .
>>>
>>> Regards,
>>>
>>>
>>> --
>>> *--*
>>>
>>> *Ignasi Garriga Sala* Coagulation Software Developer
>>>
>>> Roche Diagnostics SL
>>> Patient Care POC
>>> Av. de la Generalitat, 171-173
>>> E-08174 Sant Cugat del Vallès
>>>
>>> M +34 619 048 267
>>> *ignasi.garr...@roche.com* 
>>>
>>> roche.es  | AularioRoche
>>>  | RocheDialog
>>>  | Twitter
>>>  | YouTube 
>>> | Facebook  | LinkedIn
>>> 
>>>
>>> *Confidencialidad* - Este mensaje ha sido dirigido sólo al destinatario
>>> o a los destinatarios mencionados y puede contener información confidencial
>>> y/o de uso restringido a profesionales de la salud, en cuyo caso su
>>> remisión a terceros que no sean profesionales de la salud no está
>>> permitida. Si usted tiene dudas respecto a quién puede remitir este mensaje
>>> y/o la información que contiene, por favor, consulte con su remitente. Si
>>> usted no debería haber recibido este correo o piensa que el destinatario es
>>> incorrecto, por favor contacte con el remitente y borre este mensaje. El
>>> uso no autorizado de la información contenida en este mensaje está
>>> prohibido.
>>>
>>> *Protección de datos* - Roche Diagnostics, S.L.U. (con domicilio en
>>> Avda. de la Generalitat, 171-173, 08174 Sant Cugat del Vallès, Barcelona)
>>> es el responsable del tratamiento de sus datos de contacto corporativos con
>>> el fin de poder mantener relaciones con usted o con la empresa, entidad y
>>> organización para la cual usted trabaja o colabora. Para obtener más
>>> información sobre cómo tratamos sus datos y cómo ejercer sus derechos,
>>> consulte nuestra política de privacidad
>>> 

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

[Nandor Soma Abonyi]

+1 (non-binding)

Went through the release helper guide.
Connected to NiFi registry, imported and committed some flows.

Verified for regression:
- Azure ADLS and Blob_v12 related flows
- MQTT related flows

Noticed two issues:
- Sometimes `./bin/nifi.sh start --wait-for-init` incorrectly reports that 
"NiFi is not running. Stopped waiting for it to initialize.” while it was 
started successfully.
  I don’t consider it a blocker, will try to investigate it further.
- In ConsumeMQTT when `Add attributes as fields` is true and using 
AvroRecordSetWriter, the appended field values are null. While they have the 
correct values when using JsonRecordSetWriter.
  Checked with older versions and it is a long standing issue, hence I don’t 
consider it as a blocker. Opened a Jira to track it. [1]

Apache Maven 3.9.0 (9b58d2bad23a66be161c4664ef21ce219c2c8584)
Java version: 1.8.0_362, vendor: Temurin
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "6.3.4-orbstack-00151-g5c9dc5b64d8c", arch: 
"aarch64", family: "unix

Thanks for RM'ing Joe!

Regards,
Soma

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


> On 2023. Jun 6., at 23:38, 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:
> 5f6da64e75a2d5446f1f274fe3de7e97290f5b916eabbc0491a99c6db33f74fbdea001b403044e75bc5c2183fb0500dfc143d0f4cba19d3511f866fff774d7f5
> 
> 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
> 
> 186 issues were closed/resolved for this release:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12353069
> 
> Release note highlights can be found here:
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.22.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.22.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...