Hello Apache NiFi Community,
I am pleased to be calling this vote for the source release of Apache NiFi
NAR Maven Plugin 2.0.0. This new release is intended to be used with NiFi
2+.
The source being voted upon, including signatures, digests, etc. can be
found at:
no breaking changes, I recommend a version 1.6.0 release
> before a 2.0.0 release of the plugin.
>
> Regards,
> David Handermann
>
> On Tue, May 21, 2024 at 10:19 AM Pierre Villard
> wrote:
> >
> > Given that the flow analysis rules are something specific to NiFi
.x anyway.
Le mar. 21 mai 2024 à 15:40, David Handermann
a écrit :
> Thanks Pierre, sounds good!
>
> Regards,
> David Handermann
>
> On Tue, May 21, 2024 at 8:36 AM Pierre Villard
> wrote:
> >
> > Thanks will go ahead with 1.6.0 release process
> >
> &
lean towards 1.6.0 since the commits seem to be improvements rather
> > than bug fixes for a patch.
> >
> > On Mon, May 20, 2024 at 1:08 PM Pierre Villard
> > wrote:
> > >
> > > Hi all,
> > >
> > > We just merged a couple of improvements for the
Hi all,
We just merged a couple of improvements for the NiFi NAR Maven Plugin and
another improvement has been merged some time ago for which the community
expressed interest [1]. I think it could be a good time to release a new
version, either as 1.5.2 or as 1.6.0. Once we have a new release,
Hey guys, what's the latest on this?
Le sam. 23 mars 2024 à 01:49, Mike Thomsen a
écrit :
> Fair enough, Joe.
>
> Matt,
>
> I poked around your branch a little this evening. I agree with you and
> David 100% now on the need for some sort of abstraction. I think the Graph
> Bundle's model could
+1 (binding)
Went through the usual steps, deployed a secured cluster with a secured
NiFi Registry instance on GCP and tested a bunch of flows that I have
around.
Thanks for RM'ing David!
Le jeu. 16 mai 2024 à 15:26, Matt Burgess a écrit :
> +1 (binding)
>
> Ran through release helper,
+1 (binding)
Went through the usual steps
Built on MacOS X.
Tested a basic flow tailing a local file, doing some transformations and
sending data with InvokeHTTP to a NiFi instance with FlowFile format.
Thanks team for taking care of this release and the exciting upcoming 1.0.
Le mer. 15 mai
This will likely motivate a 1.26.1 release. I should be able to do that
next week as I'm traveling for the rest of this week.
Thanks,
Pierre
Le jeu. 9 mai 2024 à 05:01, Joe Witt a écrit :
> Eduardo
>
> Yes this was found/fixed today[1]
>
> Sorry for the trouble
>
> [1]
Apache NiFi Community,
I am pleased to announce that the 1.26.0 release of Apache NiFi passes:
10 +1 (binding) votes
7 +1 (non-binding) votes
0 0 votes
0 -1 votes
Thanks to all who helped make this release possible!
The release artifacts will be published in the next 24 hours.
t; > 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
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
gt; > > > > move the module from an optional profile to part of the standard
> > > > > build. That would make the release candidate build and review
> process
> > > > > simpler, not requiring the optional build profile.
> > > > >
> > > &
Thanks David, I'm happy to take care of a 1.26 release at the same time.
Regarding the M3 release, should the new UI be included and instructions
given on how to access it to start collecting feedback? I'm under the
impression that almost all of the work has been done, no?
Thanks,
Pierre
Le
Hi,
If you're using NiFi 2.0, then you can use Python. I recommend the below
resources:
https://www.youtube.com/watch?v=9Oi_6nFmbPg
https://nifi.apache.org/documentation/nifi-2.0.0-M2/html/python-developer-guide.html
HTH,
Pierre
Le mer. 17 avr. 2024 à 15:18, Usha Kiran Mahato
a écrit :
> Hi
I'm a +1 with this approach. Being able to use the Python extensions in
MiNiFi cpp is great!
Thanks,
Pierre
Le mar. 16 avr. 2024 à 18:39, Gábor Gyimesi a écrit :
> Hi community,
>
> I'd like to initiate a discussion about the next release of MiNiFi C++. The
> last release was more than seven
2 release is sufficiently
> production worthy for our individual use cases, is there a list of the
> remaining items/known key gaps/etc to get in so we can make a decision if
> those remaining items are noteworthy to our cases?
>
> Thanks,
> Ryan
>
> On Mon, Mar 11, 2024 at 11:50 AM
Hi Robert,
I'd expect an M3 release in the next couple of weeks and the first official
2.0 release should happen in the next couple of months I think. There is no
official timeline as it depends on the community efforts around the
remaining things we want to get it as well as the feedback from
Hi Dan,
As you can see on the doc there is a 'b' next to CONTAINS_SUBSTR and the
documentation explains its meaning:
The ‘C’ (compatibility) column contains value:
> ‘*’ for all libraries,
> ‘b’ for Google BigQuery (‘fun=bigquery’ in the connect string),
> ‘c’ for Apache Calcite (‘fun=calcite’
Hi,
NiFi is OS-agnostic for linux based distributions. You can download the
tar.gz from the download page of the website and follow the instructions to
get started on CentOS 7.
HTH,
Pierre
Le mar. 5 mars 2024 à 14:07, Gleb Efimov a écrit :
> Good afternoon I'm trying to deploy NiFi 2.0.0-M2
The Apache NiFi Team is pleased to announce the release of Apache NiFi
1.25.0.
Apache NiFi is an easy to use, powerful, and reliable system to
process and distribute data.
https://nifi.apache.org
The release artifacts can be downloaded from the project website.
Apache NiFi Community,
I am pleased to announce that the 1.25.0 release of Apache NiFi passes:
6 +1 (binding) votes
8 +1 (non-binding) votes
0 0 votes
0 -1 votes
Thanks to all who helped make this release possible!
The release artifacts will be published in the next 24 hours.
tion guide, verified hashes and
> > > signatures,
> > > > > ran
> > > > > >> a
> > > > > >>> full build on NiFi with contrib-check successfully.
> > > > > >>>
> > > > > >>> Environment:
Hi,
There is no attached image in your email.
Thanks,
Pierre
Le mar. 30 janv. 2024 à 17:12, Durante Lorenzo a
écrit :
> Good morning,
>
>
>
> I would like to engage in a discussion with you regarding some
> functionalities of Apache NiFi, to assess its potential application in a
>
LogAttribute can log the flowfile's content. Set Log Payload to true.
HTH,
Pierre
Le sam. 27 janv. 2024 à 18:45, Kumar Kapil a
écrit :
> Hi to NIFI dev team,
>
>
>
> I have below requirements where documentation or your assistance is
> required in the logging. Currently LogMessage and
Hi David,
While I agree with your summary, I have a concern here which is about user
awareness of this feature. We've seen in the past: as soon as we don't
include NARs in the convenience binary, we see that users have no clue
about those NARs (and some are super powerful/useful). I agree that
Team,
I am pleased to be calling this vote for the source release of Apache NiFi
1.25.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
gt; > Good point, since registry client is an extension point, using the
> > rules on NiFi side allows it to work for any registry client.
> >
> > On Wed, Jan 17, 2024 at 11:49 AM Pierre Villard
> > wrote:
> >>
> >> Yeah so the more I thin
Hi Christhian,
This is a known issue and will be fixed in the upcoming 2.0-M2 release that
should go out very soon.
Thanks,
Pierre
Le jeu. 18 janv. 2024 à 06:40, Cristhian Alvarez Cifuentes <
kristhian_...@hotmail.com> a écrit :
> Hi Nifi Team, how are you?
>
> i got a problem with toolkit...
gt;
> > > > HI,
> > > >
> > > > I think, both of you are correct, my initial example of the possible
> > > usage was not the best. Having a control over committing versions for
> flows
> > > is maybe the most important benefit we can gain. Contrary to naming
> &g
rite to a bucket they shouldn't be writing
> to?).
>
> On Wed, Jan 17, 2024 at 8:53 AM Pierre Villard
> wrote:
> >
> > I do think this would be a good idea. That would provide users of the
> NiFi
> > Registry a way to implement custom conditions on w
I do think this would be a good idea. That would provide users of the NiFi
Registry a way to implement custom conditions on what can be versioned or
not based on their requirements. Right now if one has write permissions for
a bucket/flow, you could commit anything as a new version which could
Sounds good to me David. As discussed on another thread, I am happy to take
care of a 1.25 release as well to have some of the fixes we added there for
migrating to 2.0.
Thanks,
Pierre
Le mar. 16 janv. 2024 à 00:44, Joe Witt a écrit :
> Wonderful progress. Definitely time and an M2 seems like
Hi,
The jython engine has been completely removed in NiFi 2.0 in favor of the
new Python API allowing you to build NiFi components in Python. Only
Clojure and Groovy are supported in NiFi 2.x.
Thanks,
Pierre
Le sam. 13 janv. 2024 à 18:47, Michael Byron
a écrit :
> Dear Apache NiFi Developers,
Hi Martin,
I do think that having a NiFi 1.25 release soon would make sense. It would
be nice to have a release that contains
https://issues.apache.org/jira/browse/NIFI-12524 which can also be seen as
an annoyance to upgrade to 2.0-M1.
I'm happy to take care of the RM duties if there is a
This is great, thanks to all the people contributing to this, I know it's a
significant amount of work and it's amazing to see this getting real!
Le jeu. 4 janv. 2024 à 09:57, Lucas Ottersbach
a écrit :
> The new site looks refreshing.
>
> Thank you James, David and all others contributing to
t; why it seems better to evaluate a resilient storage solution instead of a
> composite solution.
>
> Regards,
> David Handermann
>
> On Mon, Dec 11, 2023, 6:23 AM Pierre Villard
> wrote:
>
> > Hi David and Bryan, thanks for the feedback.
> >
> &
tate management
> > could have other benefits, but it also adds a layer of complexity that
> > may not even achieve the desired outcome, depending on the
> > capabilities of the underlying storage implementations.
> >
> > With that background, I think it would be worth evaluating
Team,
I just published a feature proposal here:
https://cwiki.apache.org/confluence/display/NIFI/State+Management+improvements+for+Disaster+Recovery+scenarios
This feature proposal is to provide a more detailed explanation around the
two below JIRAs:
The Apache NiFi Team is pleased to announce the release of Apache NiFi
1.24.0.
Apache NiFi is an easy to use, powerful, and reliable system to process and
distribute data.
https://nifi.apache.org
The release artifacts can be downloaded from the project website.
Apache NiFi Community,
I am pleased to announce that the 1.24.0 release of Apache NiFi passes:
8 +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 vote thread:
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 V
+1 (binding)
Went through the usual steps. Everything LGTM.
Very excited by this first milestone for NiFi 2.0!
Thanks David for RM'ing!
Le ven. 24 nov. 2023 à 17:37, Csaba Bejan a écrit :
> +1 (binding)
>
> - Went through the helper guide and did a clean build
> - Verified signatures and
Team,
I am pleased to be calling this vote for the source release of Apache NiFi
1.24.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
> > > Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546)
> > > > Java version: 1.8.0_392, vendor: Azul Systems, Inc.
> > > > OS name: "mac os x", version: "14.1.1", arch: "aarch64", family:
> "mac"
> > >
Team,
I am pleased to be calling this vote for the source release of Apache NiFi
1.24.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
earchClientServiceImpl/index.html
> > >
> > > I confirmed that in the path
> nifi-1.24.0/work/docs/components/org.apache.nifi/nifi-elasticsearch-client-service-nar/1.24.0
> the additionalDetails.html file doesn’t exist.
> > >
> > > Is anyone else seeing the sam
Team,
I am pleased to be calling this vote for the source release of Apache NiFi
1.24.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
Killing this RC2 in light of the license/notice issue.
Will include a few additional commits in the RC3 that I'll start later
today or tomorrow.
Le mer. 15 nov. 2023 à 16:31, Pierre Villard
a écrit :
> Team,
>
> I am pleased to be calling this vote for the source release of Apache NiFi
Team,
I am pleased to be calling this vote for the source release of Apache NiFi
1.24.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
gt;
> Regards,
> David Handermann
>
> On Tue, Nov 14, 2023 at 11:02 AM Pierre Villard
> wrote:
> >
> > Team,
> >
> > I am pleased to be calling this vote for the source release of Apache
> NiFi
> > 1.24.0.
> >
> > Please review the following guide f
Team,
I am pleased to be calling this vote for the source release of Apache NiFi
1.24.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
e:
> >
> > Hey Pierre,
> >
> > I ran into a couple of issues (they appear to be timing issues) around
> the Python stuff on startup. I think we need to hold off on the release
> until these are resolved but I think I should have a PR up some time
> tomorrow hope
Hey David,
With all of the recent changes we merged, I believe we are in the right
spot to start the process with 1.24 and 2.0M1 releases.
Happy to help with this,
Pierre
Le ven. 3 nov. 2023 à 22:46, David Handermann
a écrit :
> Team,
>
> We have made great progress on a large number of
Hi,
No, the corresponding pull request has not been merged. You can see the
full discussion here https://github.com/apache/nifi/pull/6053 and the PR
has been closed until further improvements are made. I believe there is a
custom NAR that is made available by some community members in the
>
> Rather, I’d say it's an UPLOAD_FILE event. So I’d lean more toward an
> uploadFile() method on ProvenanceReporter that takes as an argument a
> `File` (as well as a FlowFile). The size would come from the File itself,
> and the event would convey the information about the local file that was
>
Hey Bence and team,
I'd definitely be in favor of a better approach here. When removing
variables, I found myself with the need to update a lot of copies of
nifi.properties as well as other configuration files across many places of
the codebase. I don't know what is the best option/approach here
Hey Joe,
Definitely a +1 to get a M1 release ASAP. I'd still recommend waiting on
the flow.xml removal work to be merged. The reason being that users may
give useful feedback when they'll try NiFi 2.0 with existing flows coming
from NiFi 1.x and getting rid of all of the XML based stuff. There is
Hi,
Do you have an example of input and the output you'd expect? There are a
few options in terms of processors you could use and you may be able to get
things working the way you want without using JOLT.
Pierre
Le lun. 18 sept. 2023 à 22:05, Mark Woodcock a
écrit :
> Howdy,
>
> What I'm
I think NiFi 2.x going to Java 21 for all the reasons outlined makes a
> lot
> > of sense.
> >
> > Is there a timeline for 2.x?
> >
> > On Mon, Sep 11, 2023 at 5:00 AM Pierre Villard <
> > pierre.villard...@gmail.com>
> > wrote:
> >
> > &
Hi Dirk,
You're definitely not the odd one out there using JS with NiFi. The most
common usage is definitely Groovy but I'm aware of NiFi users using JS. I'm
not aware of a specific timeline as I don't know if someone in the
community is actively looking into it right now but I agree that this
ut those same organizations might also be
> > hesitant to move to NiFi 2.0. We will continue to support java 17 & NiFi
> > 1.x for some time, so hopefully those groups will have the time they need
> > to get approvals, do evaluations, and upgrade.
> >
> > Brandon
> &
Hi all,
I share the concerns raised by Chris regarding how quickly users of NiFi
will be able to adopt Java 21.
While I'm definitely in favor of using the latest and greatest, especially
when it brings to the table such significant features, we need to be
careful as it may significantly delay
+1 (binding)
Build on u20, tested a couple of simple flows.
Thanks!
Le jeu. 31 août 2023 à 19:35, Arpad Boda a écrit :
> +1 (binding)
>
> Verified signature, hashes.
> Built on debian and mac.
>
> Executed all tests successfully, verified c2 functionality, designed
> multiple flows, verified
+1
Le jeu. 24 août 2023 à 17:04, Joe Witt a écrit :
> +1 a lot of nice things in there!
>
> On Thu, Aug 24, 2023 at 7:52 AM Martin Zink wrote:
>
> > Hi community,
> >
> > I'd like to initiate a discussion about the next release of MiNiFi C++.
> The
> > last release was more than four months
Hi,
Can you clarify your question? I'm not sure I understand what you mean.
Le jeu. 20 juil. 2023 à 17:58, Ravi Kumar Undapalli
a écrit :
> Hi Team,
>
> I'm not able to use runtime attributes in lists3 processor in Apache NiFi.
>
> Thanks and regards
> Ravi Kumar Undapalli
>
I do think this provides great value. The possibility to get access to
status history of the components and at system level across restart is a
great improvement for NiFi troubleshooting. It also gives the ability to
store this information for a longer period of time. I'm definitely in favor
of
Hi,
I reopened the pull request. I'm not very familiar with the code of those
processors so I'm not sure I'm well positioned to help with the review.
However I'd recommend trying to add unit tests that exhibit the issue and
demonstrate that this is solved by your code change. I understand this
Hi,
There are still many things we want to do before an alpha release of NiFi
2.0. I'd not expect it before September at best.
Pierre
Le jeu. 6 juil. 2023, 21:15, Monteragi a écrit :
> Hi,
>
> I tried but didn't find any estimates for Nifi 2.0 release. Could someone
> please let me know
Hey Joe,
I'd recommend doing the move right now and say that NiFi 2.0 requires Java
17. And we would focus on Java 21 with NiFi 3.0.
I honestly don't see any value in absolutely keeping support for Java 11
right now.
Pierre
Le mer. 31 mai 2023 à 19:22, Joe Witt a écrit :
> Team,
>
> We've
Brian,
I would expect a PR to OTEL's java auto instrumentation project over the
> next few months that adds NiFi to its list of instrumentations. If the NiFi
> committers would like a demo / tech exchange to go over the current state
> of the tracing agent, we'd be happy to accommodate. As it
Your image didn't go through, can you copy paste the error instead?
Also I'd recommend using the users mailing list instead of the dev one.
Thanks,
Pierre
Le dim. 23 avr. 2023 à 02:02, Ari Marhali a écrit :
> Hi,
> I tried installing NiFi multiple times today, both version 1.20 and 1.21
> and
+1 binding
Went through the usual steps. Deployed a 3 node secured cluster on GCP with
a secure NiFi Registry. Tested some flows. All good.
Thanks Joe for taking care of the release!
Le jeu. 6 avr. 2023 à 05:11, Mark Bean a écrit :
> +1 (non-binding)
>
> Verified signatures and hashes.
>
+1 for a 1.20.1 - we also fixed a few bugs around NiFi Registry
Le jeu. 9 mars 2023 à 21:01, Joe Witt a écrit :
> Team,
>
> I'm thinking we should kick out a 1.20.1.
>
> This one is pretty annoying and we've seen a few folks hit it
> https://issues.apache.org/jira/browse/NIFI-11189
>
> I'll
+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
Hi,
ValidateCSV was released before and is using a specific library that is
allowing you to define specific rules on what the CSV should contain (like
for a given column that should contain numerical values, confirm the values
are in a specific range, etc) [1]. ValidateRecord would only check
Documentation is available from the NiFi UI: top right hamburger menu /
help. It'll give the documentation for your exact version.
HTH,
Pierre
Le lun. 9 janv. 2023 à 23:35, Anzalone, Paul - US
a écrit :
> Hello,
>
> I asked this question in the slack channel too. Feel free to answer in
>
+1 binding
Le mar. 13 déc. 2022 à 12:32, Marton Szasz a écrit :
> +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 <
> exceptionfact...@apache.org> wrote:
> > >
> > > Team,
> > >
> > >
Thanks for putting this together David. This is an excellent writeup and
it's great to have a release where we focus on tech debt as well as making
sure we stay up to date with our dependencies and what we support. This is
a great opportunity for us to clean a lot of things in our code and I can't
IMO we should start working on NiFi 2.0 going forward and it sounds like a
good opportunity to make such changes in our components.
Le mar. 25 oct. 2022 à 19:33, Mike Thomsen a
écrit :
> The hash-based deduplication strategy used the built-in "md5"
> attribute to offload the work to the
Hi Dan,
I personally think this is a fair addition to the expression language
options we have. Feel free to file a JIRA and submit a pull request if
you'd like to do so.
Thanks,
Pierre
Le ven. 7 oct. 2022 à 08:34, Dan S a écrit :
> My team has flow file attributes which we do not always know
I believe this is what we're already doing for NiFi Registry and its
supported databases:
https://github.com/apache/nifi/tree/main/nifi-registry/nifi-registry-core/nifi-registry-test
Pierre
Le mer. 28 sept. 2022 à 19:22, Mike Thomsen a
écrit :
> We've been successfully using testcontainers
+1 binding
went through the usual steps, deployed a secured cluster with secured NiFi
Registry, executed my usual flows, everything is looking good
Thanks Joe for taking care of this release!
Le ven. 29 juil. 2022 à 14:06, Robert Fellows a
écrit :
> +1 (non-binding)
>
> Ran through the
+1 (binding)
Went through the usual steps and deployed a secured cluster with secured
NiFi Registry to run some flows.
Built on Mac OS Monterey 12.4
Apache Maven 3.8.2 (ea98e05a04480131370aa0c110b8c54cf726c06f)
Java version: 1.8.0_302, vendor: Azul Systems, Inc., runtime:
An option is to set the destination of the reporting task to
https://${hostname(true)}:PortNumber so
that expression language is used to get the hostname of the node. Based on
your warning message, this is a network issue so using the local FQDN may
be better.
Le jeu. 14 juil. 2022 à 20:17, a
Hi,
Monitoring in NiFi is one of my favorite topics and I do think
OpenTelemetry would be of great value. There is never too much
observability in a software like NiFi when it comes to integrating anything
with anything. I'm more than happy to be part of the discussion in terms of
I'd even love to go straight to Java 17 since it's the new LTS version...
but this may be quite a big jump for our community and users.
I guess we can envision a "short" 2.x release line and consider Java 17 for
3.x.
Definitely approve the proposal!
Le mer. 15 juin 2022 à 18:50, Kevin Doran a
+1 (binding)
Went through the usual steps (build, signature, etc) and deployed a secured
NiFi cluster and NiFi Registry in GCP.
Thanks Joe for taking care of this release!
Thanks,
Pierre
Le mar. 14 juin 2022 à 17:19, Adam Debreceni a
écrit :
> +1 (non-binding)
>
> Verified signature, hashes.
+1
Le mar. 17 mai 2022 à 10:02, Ádám Markovics a écrit :
> Hi,
> I also think it's time for a new release.
> Regards,
>
> Ádám
>
> On Mon, May 16, 2022 at 5:32 PM Marton Szasz wrote:
>
> > I agree that it's time for a new release, thanks for RM'ing Martin.
> >
> > I have these two issues that
+1 (binding)
Went through the usual steps. Deployed a secured cluster with secured NiFi
Registry in GCP. Deployed usual/common flows. Looking good to me.
Thanks Joe for taking care of this release.
Pierre
Le jeu. 28 avr. 2022 à 00:52, Peter Turcsanyi a
écrit :
> +1 (non-binding)
>
> Ran
Hi Dharani,
I confirm that NiFi 1.16.0 has been released a few weeks ago now and we're
about to start the release process for a 1.16.1 release. I'd recommend
waiting for this release if you can, it should be available by next week I
think (no promises though).
Thanks,
Pierre
Le mar. 19 avr.
Congrats Adam!
Le lun. 28 mars 2022 à 16:11, Kevin Doran a écrit :
> Congrats, Adam!
>
> On Mar 28, 2022 at 10:08:24, Otto Fowler wrote:
>
> > Congratulations!
> >
> > From: Marton Szasz
> > Reply: dev@nifi.apache.org
> > Date: March 25, 2022 at 08:50:07
> > To: dev@nifi.apache.org
> >
+1 (binding)
Went through the usual steps.
Thanks Joe!
Le mar. 18 janv. 2022 à 04:27, Joe Gresock a écrit :
> +1 (non-binding)
>
> Verified signatures and hashes, built from source (MacOS 11.6, Azul Zulu
> 1.8.0_292), ran a 3-node cluster and some basic flows.
>
> On Mon, Jan 17, 2022 at 6:20
+1 (binding)
Went through the usual steps and confirmed the use of the correct log4j
transitive dependencies.
Thanks for taking care of the release Joe.
Pierre
Le mer. 22 déc. 2021 à 11:17, Kotaro Terada a écrit :
> +1 (non-binding)
>
> - Verified signatures and hashes.
> - Built from source
Congrats Margot!
Le mer. 15 déc. 2021 à 20:00, Kevin Doran a écrit :
> Congratulations Margot! Well deserved.
>
> > On Dec 15, 2021, at 13:47, Joe Witt wrote:
> >
> > Congrats Margot! And thanks
> >
> > On Wed, Dec 15, 2021 at 11:46 AM Matt Gilman
> wrote:
> >
> >> Apache NiFi community,
>
+1 (binding)
Went through the usual steps.
Thanks for taking care of this so quickly!
Pierre
Le mer. 15 déc. 2021 à 10:55, Kotaro Terada a écrit :
> +1 (non-binding)
>
> - Verified signatures and hashes.
> - Built from source with OpenJDK 8 and OpenJDK 11.
> - Ran and tested a couple of
https://issues.apache.org/jira/browse/NIFI-9482
Le mer. 15 déc. 2021 à 09:44, Ganesh, B (Nokia - IN/Bangalore) <
b.gan...@nokia.com> a écrit :
> Hi All ,
>
> According to latest mitigation plan from Log4J - (
> https://logging.apache.org/log4j/2.x/security.html) Java 8 (or later)
> users should
+1 binding
Went through the usual steps, built sources and tested a simple flow.
Le mar. 7 déc. 2021 à 10:53, Ferenc Gerlits a écrit :
> +1 (non-binding)
>
> - checked signatures and hashes
> - compared the source to the tag in the repo
> - connected to C2 using TLS
> - ran a simple GetFile ->
+1 (binding)
Le mer. 1 déc. 2021 à 20:30, Otto Fowler a écrit :
> +1 (non-binding)
> ran through the testing guide
>
> From: Bryan Bende
> Reply: dev@nifi.apache.org
> Date: November 30, 2021 at 15:56:38
> To: dev@nifi.apache.org
> Subject: [VOTE] Release Apache NiFi NAR Maven Plugin
+1 (binding)
Followed the usual steps to build the agent on my MBP and test it with a
simple flow.
Thanks Adam for taking care of this release!
Pierre
Le mer. 24 nov. 2021 à 10:49, Ádám Markovics a
écrit :
> +1 (non-binding)
> Verified and built on Ubuntu 20.04. Ran tests and also ran a
1 - 100 of 487 matches
Mail list logo
