ptionfact...@apache.org> wrote:
> > >
> > > Team,
> > >
> > > Following positive feedback on NiFi 2.0 Proposed Release Goals [1] on
> the
> > > recent discussion thread [2], I am calling this vote to adopt the
> following
> > > as Release Goals for NiFi 2.0:
+1 (binding)
On Tue, 13 Dec 2022 at 09:04, Ferenc Erdei wrote:
>
> +1 (non-binding)
>
> > On 2022. Dec 12., at 18:02, David Handermann
> > wrote:
> >
> > Team,
> >
> > Following positive feedback on NiFi 2.0 Proposed Release Goals [1] on the
> &
Hello,
The Apache NiFi team would like to announce the release of Apache NiFi
MiNiFi C++ 0.13.0.
New features in this release:
- New processors:
- ListenTCP
<https://github.com/apache/nifi-minifi-cpp/blob/rel/minifi-cpp-0.13.0/PROCESSORS.md#listentcp>
- PutTCP
<https://github.c
+1 (non-binding)
> On 2022. Dec 12., at 18:02, David Handermann
> wrote:
>
> Team,
>
> Following positive feedback on NiFi 2.0 Proposed Release Goals [1] on the
> recent discussion thread [2], I am calling this vote to adopt the following
> as Release Goals for NiFi 2.
+1 (non-binding)
> On 2022. Dec 12., at 18:02, David Handermann
> wrote:
>
> Team,
>
> Following positive feedback on NiFi 2.0 Proposed Release Goals [1] on the
> recent discussion thread [2], I am calling this vote to adopt the following
> as Release Goals for NiFi 2.
+1 (non-binding)
> On Dec 12, 2022, at 6:02 PM, David Handermann
> wrote:
>
> Team,
>
> Following positive feedback on NiFi 2.0 Proposed Release Goals [1] on the
> recent discussion thread [2], I am calling this vote to adopt the following
> as Release Goals for NiFi
+1 (binding)
> On Dec 12, 2022, at 12:02 PM, David Handermann
> wrote:
>
> Team,
>
> Following positive feedback on NiFi 2.0 Proposed Release Goals [1] on the
> recent discussion thread [2], I am calling this vote to adopt the following
> as Release Goals for NiFi 2.
hard to know what the real name was, a recent release
added a new column in the documentation called "API Name". Example for
ConsumeKafka_2_6 processor:
https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-2-6-
+1 (non-binding)
David Handermann schrieb am Mo., 12. Dez.
2022, 18:02:
> Team,
>
> Following positive feedback on NiFi 2.0 Proposed Release Goals [1] on the
> recent discussion thread [2], I am calling this vote to adopt the following
> as Release Goals for NiFi 2.0:
>
+1 (non-binding)
> On 2022. Dec 12., at 18:02, David Handermann
> wrote:
>
> Team,
>
> Following positive feedback on NiFi 2.0 Proposed Release Goals [1] on the
> recent discussion thread [2], I am calling this vote to adopt the following
> as Release Goals for NiFi 2.
inspection tools to see how the request is submitted
by NiFi fronted, alternatively checking the name in the source code.
Moving to 2.0, would it be good to standardize on PropertyDescriptor$name
and displayname?
Thanks,
Mathew.
[1] https://github.com/Chaffelson/nipyapi
On Mon, 12 Dec 2022 at 19:46
+1 (binding)
On Mon, Dec 12, 2022 at 12:02 PM David Handermann
wrote:
>
> Team,
>
> Following positive feedback on NiFi 2.0 Proposed Release Goals [1] on the
> recent discussion thread [2], I am calling this vote to adopt the following
> as Release Goals for NiFi 2.0:
&g
+1 (binding)
On Dec 12, 2022 at 12:41:16, Matt Gilman wrote:
> +1 (binding)
>
> On Mon, Dec 12, 2022 at 12:02 PM David Handermann <
> exceptionfact...@apache.org> wrote:
>
> Team,
>
>
> Following positive feedback on NiFi 2.0 Proposed Release Goals [1] on th
+1 (non-binding)
On Mon, Dec 12, 2022, 6:42 PM Matt Gilman wrote:
> +1 (binding)
>
> On Mon, Dec 12, 2022 at 12:02 PM David Handermann <
> exceptionfact...@apache.org> wrote:
>
> > Team,
> >
> > Following positive feedback on NiFi 2.0 Proposed Release
+1 (binding)
On Mon, Dec 12, 2022 at 12:02 PM David Handermann <
exceptionfact...@apache.org> wrote:
> Team,
>
> Following positive feedback on NiFi 2.0 Proposed Release Goals [1] on the
> recent discussion thread [2], I am calling this vote to adopt the following
> as Relea
+1 (binding)
> On Dec 12, 2022, at 12:02 PM, David Handermann
> wrote:
>
> Team,
>
> Following positive feedback on NiFi 2.0 Proposed Release Goals [1] on the
> recent discussion thread [2], I am calling this vote to adopt the following
> as Release Goals for NiFi 2.
+1 (binding)
On Mon, Dec 12, 2022 at 12:27 PM Chris Sampson
wrote:
>
> +1 (non-binding)
>
>
> Cheers,
>
> ---
> Chris Sampson
> IT Consultant
> chris.samp...@naimuri.com
>
>
> > On 12 Dec 2022, at 17:02, David Handermann
> > wrote:
> >
>
+1 (non-binding)
Cheers,
---
Chris Sampson
IT Consultant
chris.samp...@naimuri.com
> On 12 Dec 2022, at 17:02, David Handermann
> wrote:
>
> Team,
>
> Following positive feedback on NiFi 2.0 Proposed Release Goals [1] on the
> recent discussion thread [2], I am calli
+1 binding
On Mon, Dec 12, 2022 at 10:02 AM David Handermann <
exceptionfact...@apache.org> wrote:
> Team,
>
> Following positive feedback on NiFi 2.0 Proposed Release Goals [1] on the
> recent discussion thread [2], I am calling this vote to adopt the following
> as Relea
Team,
Following positive feedback on NiFi 2.0 Proposed Release Goals [1] on the
recent discussion thread [2], I am calling this vote to adopt the following
as Release Goals for NiFi 2.0:
1. Remove Java 8 support and require Java 11
2. Remove deprecated components
3. Remove deprecated component
.
Regards,
David Handermann
On Mon, Dec 12, 2022 at 4:12 AM Isha Lamboo
wrote:
> Hi all,
>
> This may be too basic/self-explanatory to count as a goal at all, but will
> site-to-site interoperability between NiFi 1.x and NiFi 2.x nodes will be
> preserved?
>
> Regards,
>
> I
Hi all,
This may be too basic/self-explanatory to count as a goal at all, but will
site-to-site interoperability between NiFi 1.x and NiFi 2.x nodes will be
preserved?
Regards,
Isha
-Oorspronkelijk bericht-
Van: David Handermann
Verzonden: zondag 11 december 2022 04:08
Aan: Otto
Apache NiFi Community,
I am pleased to announce that the 0.13.0 release of Apache NiFi MiNiFi C++
passes with
3 +1 (binding) votes
3 +1 (non-binding) votes
0 0 votes
0 -1 votes
Thanks to all who helped make this release possible.
Here is the PMC vote thread:
https://lists.apache.org
r 10, 2022 at 10:46:51
> To: dev@nifi.apache.org
> Subject: Re: [DISCUSS] Finalizing Release Goals for NiFi 2.0
>
> Thanks for the additional feedback Ryan and Kevin!
>
> There appears to be general agreement on the path forward, so I will
> initiate a vote thread soon. I'
decided and
communicated ( if not voted on ).
From: David Handermann
Reply: dev@nifi.apache.org
Date: December 10, 2022 at 10:46:51
To: dev@nifi.apache.org
Subject: Re: [DISCUSS] Finalizing Release Goals for NiFi 2.0
Thanks for the additional feedback Ryan and Kevin!
There appears to be
r than the currently stated "Requires Java 8
> >
> > or
> >
> > > Java 11", the requirement can be "Requires Java 11 or Java 17". I don't
> >
> > > think you were suggesting the minimum version be Java 17, were you?
> >
> &g
+1 (bindig)
Built and started with a simple flow on m1 mac, verified sigs and hashes.
Thanks,
Arpad
On Thu, Dec 8, 2022 at 12:38 PM Marc Parisi wrote:
> +1 (binding)
>
> Simple test capturing WEL sending to NiFi. Verified build on u22 as well,
> verifying sigs and hashes.
>
&
Hello apache devs,
Could someone review/merge:
https://issues.apache.org/jira/browse/NIFI-10608 Copied Processor Group no
longer contains non-referenced Controller Services
This has already been looked over by fellow contributor, markobean, and is
waiting on final review/commit
Thanks
+1 (binding)
Simple test capturing WEL sending to NiFi. Verified build on u22 as well,
verifying sigs and hashes.
Thanks,
Marc
On Wed, Dec 7, 2022 at 9:56 PM Marton Szasz wrote:
> +1 (binding)
>
> - Followed the release helper guide steps, everything was in good order.
> - Tes
+1 (binding)
- Followed the release helper guide steps, everything was in good order.
- Tested build on both ubuntu 22.04 / GCC 11 and windows 10, with a
wide range of extensions. Couldn't build on Arch Linux / GCC 11
because of some weird local toolchain issue that only happens on my
desktop. Als
nt can be "Requires Java 11 or Java 17". I don't
>
> > think you were suggesting the minimum version be Java 17, were you?
>
> Either
>
> > way, the issue with Java 17 needs to be identified and fixed as well as
>
> > more thorough testing to find other
ted "Requires Java 8
> or
> > Java 11", the requirement can be "Requires Java 11 or Java 17". I don't
> > think you were suggesting the minimum version be Java 17, were you?
> Either
> > way, the issue with Java 17 needs to be identified and fixed as
, the issue with Java 17 needs to be identified and fixed as well as
> more thorough testing to find other possible edge cases before we move
> forward too aggressively.
>
> [1] https://issues.apache.org/jira/browse/NIFI-10958
>
> On Wed, Dec 7, 2022 at 1:33 PM Mike Thomsen wrote:
&
m version as noted. NiFi will not be able to use
> Spring Framework 6 until Java 17 is the minimum version, so that is a key
> concern. One of the key differences in Java 17 is that it enforces
> modularization of access, so access to internal JDK classes log warnings on
> Java 11, but ca
Thanks to everyone for the feedback thus far!
Regarding making Java 11 the minimum version versus 17, it is a good
question, particularly in light of the fact that Spring Framework 6 has
made Java 17 the minimum version as noted. NiFi will not be able to use
Spring Framework 6 until Java 17 is
revision of the core framework, Spring Framework 6.0 comes
with a Java 17+ baseline and a move to Jakarta EE 9+ "
When JDK 11 is the baseline for NiFi, can it use Spring Framework 6.0?
And on Jakarta EE 9+, I see a lot of projects now switching from Javax to
Jakarta (for example Camel:
https://iss
17, were you? Either
way, the issue with Java 17 needs to be identified and fixed as well as
more thorough testing to find other possible edge cases before we move
forward too aggressively.
[1] https://issues.apache.org/jira/browse/NIFI-10958
On Wed, Dec 7, 2022 at 1:33 PM Mike Thomsen wrote:
&g
gt; Thanks,
> > Pierre
> >
> > Le mar. 6 déc. 2022 à 23:50, Joe Witt a écrit :
> >
> >> David, All,
> >>
> >> This is an excellent writeup/good framing. I am supportive of this
> >> as-is since it is achievable and lays out a clear path. We can
Hello
The Apache NiFi team would like to announce the release of Apache NiFi 1.19.1.
Apache NiFi is an easy to use, powerful, and reliable system to
process and distribute
data. Apache NiFi was made for dataflow. It supports highly
configurable directed graphs
of data routing, transformation
Apache NiFi Community,
I am pleased to announce that the 1.19.1 release of Apache NiFi passes with
4 +1 (binding) votes
4 +1 (non-binding) votes
0 0 votes
0 -1 votes
Thanks to all who helped make this release possible.
Here is the PMC vote thread:
https://lists.apache.org/thread
+1 binding
On Wed, Dec 7, 2022 at 7:21 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
> Installed, configured and ran NiFi and NiFi registry testin
+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
Installed, configured and ran NiFi and NiFi registry testing several flows
and Registry functions. During testing, verified NIFI-10939 and NIFI-10937
specifically
al
> vote on this proposal.
>
> Thanks,
> Pierre
>
> Le mar. 6 déc. 2022 à 23:50, Joe Witt a écrit :
>
>> David, All,
>>
>> This is an excellent writeup/good framing. I am supportive of this
>> as-is since it is achievable and lays out a clear path. We ca
+1 (non-binding)
-Verified signature, hashes and git commit hash
-Built it from source with all extensions on Ubuntu 22.04
-Verified the new PutTCP and ListenTCP processors with two agents
communicating with each other
Thanks,
Martin
On Mon, Dec 5, 2022 at 3:41 PM Gábor Gyimesi wrote:
> +1 (n
s achievable and lays out a clear path. We can make
> milestone releases of NiFi 2.0.0 along the way until we achieve all
> the stated goals. I assume migration bits will be the long pole and
> once we have them sorted we can kick out a 2.0.0. We already have a
> version guide that go
+1 (binding)
Ran through release helper, tested a handful of flows including one
with the new UpdateDatabaseTable processor. I verified the existence
of NIFI-10956 in this release; however it has been in multiple
releases and I put a PR up, IMO it is not a blocker and can wait until
the next
+1 binding
Verified functionality on 3 node NiFi cluster and test flows
Verified X509 login for NIFi
Verified OIDC login/logout in NiFi and NiFi Registry
Verified LDAP login/logout for NiFi and NiFi Registry
On Tue, Dec 6, 2022 at 5:56 PM Nandor Soma Abonyi
wrote:
> +1 (non-bind
+1 (non-binding)
- Went through the release helper guide.
- Tested interaction with NiFi registry.
- Ran a simple flow to verify NIFI-10785.
- Verified NIFI-10872.
Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
Java version: 1.8.0_332, vendor: Temurin
Default locale: en_US
David, All,
This is an excellent writeup/good framing. I am supportive of this
as-is since it is achievable and lays out a clear path. We can make
milestone releases of NiFi 2.0.0 along the way until we achieve all
the stated goals. I assume migration bits will be the long pole and
once we have
Team,
With the release of NiFi 1.19.0 deprecating support for Java 8, the end of
the year provides a good opportunity for finalizing general release goals
for NiFi 2.0.
Based on previous discussions from July 2021 [1] and June 2022 [2], there
seems to be general agreement with focusing a NiFi
due to lack
> of vote participation we will.
>
> I am pleased to be calling this vote for the source release of Apache
> NiFi 1.19.1.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-121
+1 (non-binding)
- Went through the helper guide and did a clean build
- Verified signatures and hashes
- Built on OSX 11.6.6
- AdoptOpenJDK (build 1.8.0_282-b08)
- Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
- Started NiFi and created a simple flow
- NIFI-10555: Verified that MiNiFi
+1 (non-binding)
- Went through the helper guide, full clean build, verified signatures and
hashes
- Started NiFi, created a simple flow with ListenHTTP
- NIFI-10701, NIFI-10857: Run minifi and minifi-c2 ITs, which includes the
building of the refactored docker images (dockermaven).
- NIFI-10679
+1 (binding)
- Verified signatures and hashes
- Ran build using Maven 3.8.6
- Ran build on Ubuntu 22.04 with Azul Zulu JDK 1.8.0-352 x86_64
- Ran build on macOS 13.0 with Azul Zulu JDK 11.0.17 AArch64
- Ran stateless and system tests on macOS 13.0 with Azul Zulu JDK 11.0.17
AArch64
- Ran NiFi on
release of Apache
NiFi 1.19.1.
The source zip, including signatures, digests, etc. can be found at:
https://repository.apache.org/content/repositories/orgapachenifi-1218
The source being voted upon and the convenience binaries can be found at:
https://dist.apache.org/repos/dist/dev/nifi/nifi
+1 (non-binding)
- Verified that binaries are no longer in the source archive
- Verified signature, hashes and git commit hash
- Built RC2 core and all extensions (excluding Tensorflow) with GCC 11.3 on
Ubuntu 22.04
- Ran all unit, integration and docker system tests
- Verified contents of README.
On Mon, Dec 5, 2022 at 2:29 PM John McGinn wrote:
> Just a note, but the issues closed/resolved list is inaccessible to the
> public. Not sure if it is meant to be that way or not.
>
> The release notes link right below it is accessible though.
>
> Thanks for raising this! It seems to be some w
pleased to be calling this vote for the source release of Apache NiFi
MiNiFi C++ 0.13.0.
The code and the binary package are identical to RC1, I have fixed a
problem with the source package. Sorry about the extra work.
The source tarball, the binary build, plus signatures and digests can be
found
+1 (non-binding)
Verified commit, hashes, signatures, built on windows, ran all unit
tests and
tested with a CWEL->LogAttribute flow.
Thank you,
Adam
On Mon, Dec 5, 2022 at 11:40 AM Ferenc Gerlits wrote:
> Hello,
>
> I am pleased to be calling this vote for the source release of
Hello,
I am pleased to be calling this vote for the source release of Apache NiFi
MiNiFi C++ 0.13.0.
The code and the binary package are identical to RC1, I have fixed a
problem with the source package. Sorry about the extra work.
The source tarball, the binary build, plus signatures and
> It seems to me that the convenience binary found its way into the source
archive.
Good catch! It has indeed, unfortunately. Sorry about that. RC2 coming
up soon.
Thanks,
Ferenc
On Fri, Dec 2, 2022 at 2:25 PM Adam Debreceni wrote:
> -1 (non-binding)
>
> It seems to me that the convenience
ered a couple of bugs. Most were minor,
> > but I would consider NIFI-10937 [1] critical enough to sink the release.
> > It results in a failure to startup nifi with a flow.xml.gz unless the
> > flow.json.gz is present. The fact that we write out both of them is a
> >
I'll take a look at the PR you submitted for it
On Fri, Dec 2, 2022 at 4:50 PM Mark Payne wrote:
> -1 (binding)
>
> In doing some testing, I encountered a couple of bugs. Most were minor,
> but I would consider NIFI-10937 [1] critical enough to sink the release.
> It res
-1 (binding)
In doing some testing, I encountered a couple of bugs. Most were minor, but I
would consider NIFI-10937 [1] critical enough to sink the release.
It results in a failure to startup nifi with a flow.xml.gz unless the
flow.json.gz is present. The fact that we write out both of them is
, and ran my prototypical flows which
> include NiFi WEC -> MiNiFi -> Kafka . Didn't notice any issues with Readme
> + NOTICE or LICENSE files
>
> Great work team!
>
> Thanks,
> Marc
>
> On Thu, Dec 1, 2022 at 1:30 PM Jeremy Dyer wrote:
>
> > +1 (binding)
>
Hello,
I am pleased to be calling this vote for the source release of Apache
NiFi 1.19.1.
The source zip, including signatures, digests, etc. can be found at:
https://repository.apache.org/content/repositories/orgapachenifi-1217
The source being voted upon and the convenience binaries can be
+1 binding.
Typical build I do with docker builds on a U22 base. Followed release
guide, confirmed sigs and hashes, and ran my prototypical flows which
include NiFi WEC -> MiNiFi -> Kafka . Didn't notice any issues with Readme
+ NOTICE or LICENSE files
Great work team!
Thanks,
Marc
gt; > One additional note for 1.19.1, the following Jira issue and associated
> > pull request just merged resolve a regression in Kafka component
> > configuration when using SCRAM-SHA-256 or SCRAM-SHA-512 as the SASL
> > Mechanism:
> >
> > https://issues.apache.org/ji
> - built RC core and all extensions (excluding Tensorflow) with GCC 11.3 on
> Ubuntu 22.04
> - ran all unit, integration and docker system tests
> - verified contents of README.md, NOTICE, and LICENSE files
> - verified
>
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-
RAM-SHA-512 as the SASL
> Mechanism:
>
> https://issues.apache.org/jira/browse/NIFI-10919
>
> Regards,
> David Handermann
>
> On Wed, Nov 30, 2022 at 1:55 PM Joe Witt wrote:
>
> > Grabbed all the goods from main post 1.19 and have them on branch
> > 'suppor
Joe,
One additional note for 1.19.1, the following Jira issue and associated
pull request just merged resolve a regression in Kafka component
configuration when using SCRAM-SHA-256 or SCRAM-SHA-512 as the SASL
Mechanism:
https://issues.apache.org/jira/browse/NIFI-10919
Regards,
David Handermann
- verified
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.13.0/nifi-minifi-cpp-0.13.0-bin-linux.tar.gz
binary with simple flows having TailFile, GetFile, LogAttribute processors
and communication through InvokeHTTP processor with NiFi's ListenHTTP
processor
- verified Prome
"The use cases for which Nifi is used/adopted does the data load belongs to
streaming mode or pure batch workloads"
Actually for both. NiFi is used for creating data flows.
Data flows can be used for:
- Data ingesting (gathering data from a lot of sources)
- Data offloading (load dat
Hi Team,
We are working on developing a Nifi connector to send and receive data from
Azure Data Explorer( a fast and fully managed data analytics service offering
for relatime analysis on large volumes of data streaming from IOT devices,
applications etc.).
We wanted to understand the general
Grabbed all the goods from main post 1.19 and have them on branch
'support/nifi-1.19'
Waiting on https://issues.apache.org/jira/browse/NIFI-10914 and then
will roll with the 1.19.1 RC.
Thanks
On Wed, Nov 30, 2022 at 8:23 AM Joe Witt wrote:
>
> Team,
>
> I'm thinkin
equently, I would like to
> try and get it in before this release.
>
> I created this JIRA [1] for the issue, and I can report back here once
> I start working on it to see if it looks like it will still be
> something to wait on.
>
> [1] https://issues.apache.org/jira/browse/NI
ee if it looks like it will still be
something to wait on.
[1] https://issues.apache.org/jira/browse/NIFI-10915
On Wed, Nov 30, 2022 at 9:43 AM David Handermann
wrote:
>
> Mark,
>
> The dependency duplication detection is a new optional goal of the NAR
> plugin. The basic
as they upgrade past 1.16.
We thought it was sorted in 1.19 but not so - as shown in
https://issues.apache.org/jira/browse/NIFI-10874. For those watching
in Slack this has been biting several users lately.
I'll sweep up existing already landed items that are easily ported over.
I do reali
Mark,
The dependency duplication detection is a new optional goal of the NAR
plugin. The basic purpose is to detect unnecessary dependencies in the
compile scope, which are already provided from a parent NAR dependency.
For example, the nifi-standard-service-api-nar includes the
nifi-ssl-context
:18 PM Kevin Doran wrote:
> Hi all,
>
> There’s been a few improvements and bug fixes to the NAR Maven Plugin. One
> nice new feature is a new maven goal that detects duplicate dependencies in
> NARs. Another contribution improves our NiFi build reproducibility.
>
> Given
Hello Apache NiFi community,
Please find the associated guidance to help those interested in
validating/verifying the release so they can vote.
# Download latest KEYS file:
https://dist.apache.org/repos/dist/release/nifi/KEYS
# Import keys file:
gpg --import KEYS
# Download the nifi-minifi-cpp
Hello,
I am pleased to be calling this vote for the source release of Apache NiFi
MiNiFi C++ 0.13.0.
The source tarball, the binary build, plus signatures and digests can be
found at:
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.13.0/
The Git tag is minifi-cpp-0.13.0-RC1
The
s been a few improvements and bug fixes to the NAR Maven Plugin.
> One
> > nice new feature is a new maven goal that detects duplicate dependencies
> in
> > NARs. Another contribution improves our NiFi build reproducibility.
> >
> > Given all this, I’d like to release a
+1 thanks Kevin
On Tue, Nov 29, 2022 at 2:18 PM Kevin Doran wrote:
>
> Hi all,
>
> There’s been a few improvements and bug fixes to the NAR Maven Plugin. One
> nice new feature is a new maven goal that detects duplicate dependencies in
> NARs. Another contribution impro
Hi all,
There’s been a few improvements and bug fixes to the NAR Maven Plugin. One
nice new feature is a new maven goal that detects duplicate dependencies in
NARs. Another contribution improves our NiFi build reproducibility.
Given all this, I’d like to release a new version of the plugin that
Hello
The Apache NiFi team would like to announce the release of Apache NiFi 1.19.0.
Apache NiFi is an easy to use, powerful, and reliable system to
process and distribute data. Apache NiFi was made for dataflow. It
supports highly configurable directed graphs of data routing,
transformation
Apache NiFi Community,
I am pleased to announce that the 1.19.0 release of Apache NiFi passes with
6 +1 (binding) votes
5 +1 (non-binding) votes
0 0 votes
0 -1 votes
Thanks to all who helped make this release possible.
Here is the PMC vote thread:
https://lists.apache.org/thread
+1 binding
On Mon, Nov 28, 2022 at 5:35 AM Peter Turcsanyi
wrote:
> +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
+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
+1 (non-binding)
- Went through the helper guide, full clean build, verified signatures and
hashes
- Started NiFi, created a simple flow
- NIFI-10701, NIFI-10857: Run minifi and minifi-c2 ITs, which includes the
building of the refactored docker images (dockermaven). Image sizes look
good
- NIFI
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/com
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
rted NiFi, designed a couple of simple flows. Locally built Docker images
and tested connectivity between NiFi, Registry and Toolkit with some simple
Flows and customer test harness.
Cheers,
---
Chris Sampson
IT Consultant
chris.samp...@naimuri.com
> On 23 Nov 2022, at 15:58, Joe Witt
+1 (binding) Ran through release helper, tested a couple of flows
including one with the new UpdateDatabaseTable processor. Thanks for
RM'ing Joe!
On Wed, Nov 23, 2022 at 10:58 AM Joe Witt wrote:
>
> Hello,
>
> I am pleased to be calling this vote for the source release of Apa
+1 binding
Verified checksums, build, signature, started NiFi, designed a simple flow.
Thanks,
Arpad
On Sat, Nov 26, 2022 at 6:41 PM Marton Szasz wrote:
> +1 (binding)
>
> Followed the usual steps and tested a use case of collecting system
> logs with minifi c++ and collecting
+1 (binding)
Followed the usual steps and tested a use case of collecting system
logs with minifi c++ and collecting them in nifi using ListenUDP.
Thanks,
Marton
On Sat, 26 Nov 2022 at 06:25, David Handermann
wrote:
>
> +1 (binding)
>
> - Verified signatures and hashes
> -
+1 (binding)
- Verified signatures and hashes
- Ran build using Maven 3.8.6
- Ran build on Ubuntu 22.04 with Azul Zulu JDK 1.8.0-345 AMD64
- Ran build on macOS 13.0 with Azul Zulu JDK 17.0.4 AArch64
- Ran stateless and system tests on macOS 13.0 with Azul Zulu JDK 17.0.4
AArch64
- Ran NiFi on
threshold, load balance strategy, prioritizers and copied PG it was
contained in.
Copied connection retained all modified settings.
Issue with backward compatibility of flow.xml.gz was noticed where removing
flow.json.gz and restarting nifi can lead to some WARN logs. Many times nifi
will
Hello,
I am pleased to be calling this vote for the source release of Apache NiFi
1.19.0.
The source zip, including signatures, digests, etc. can be found at:
https://repository.apache.org/content/repositories/orgapachenifi-1216
The source being voted upon and the convenience binaries can be
Ok it is all in. Starting RC build. Please do not tag anything else to
1.19. If necessary I'll pull things in.
1.20 has been established.
Thanks
On Tue, Nov 22, 2022 at 8:51 AM Joe Witt wrote:
> Gonna wait for https://issues.apache.org/jira/browse/NIFI-10857 as this
> was appa
1001 - 1100 of 6761 matches
Mail list logo
