, I have another open issue that is closely related to S/MIME
handling, and includes some Controller Services that could be useful in
implementing signed S/MIME emails. Feel free to provide your comments on
the related issue and PR in GitHub.
Regards,
David Handermann
On Tue, Dec 1, 2020 at 10:00
,
David Handermann
On Fri, Jan 29, 2021 at 5:33 PM M Tien wrote:
> +1 non-binding.
>
> Went through the release guide
> Verified a full build on JDK 1.8.0_275 and JDK 11.0.5
> Verified a secure instance of NiFi
> Verified I was able to authenticate with OIDC using Google, Okta, and
as well as TLS protocol
support differences on Java 8 and 11.
Confirmed absence of bcprov-ext-jdk15on from nifi-framework-nar as
documented in NIFI-8186.
Regards,
David Handermann
On Tue, Feb 2, 2021 at 12:18 PM Mark Payne wrote:
> +1 (binding)
>
> Build details:
> Apache
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.
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
:
https://issues.apache.org/jira/browse/NIFI-6714
Regards,
David Handermann
On Sat, Jun 12, 2021 at 10:31 AM MaHmOuD El-Sayed
wrote:
> .bootstrap.config.log.dir=C:\Users\MaHmOuD\DOWNLO~1\COMPRE~1\NIFI-1~1.2\bin\..\\logs
> org.apache.nifi.NiFi
> Exception in thr
Names should resolve the problem.
Here's the release notes for OkHttp 3.10.0, referencing RFC 2818, which
deprecated falling back to certificate common names for hostname
verification:
https://square.github.io/okhttp/changelog_3x/#version-3100
Regards,
David Handermann
On Thu, Jun 10, 2021 at 11
Congratulations Chris! Looking forward to your continued contributions!
Regards,
David Handermann
On Thu, May 13, 2021 at 3:38 PM Matt Burgess wrote:
> Congratulations and welcome aboard Chris!
>
> On Thu, May 13, 2021 at 4:25 PM Joe Witt wrote:
> >
> > On behalf of the
e 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.
Re
repository password property
- Tested NiFi Registry with bucket creation and NiFi process group version
control
- Test NiFi Stateless with GetFile and UnpackContent flow downloaded from
NiFi process group
Regards,
David Handermann
On Mon, Jul 12, 2021 at 6:31 AM Arpad Boda wrote:
> +1 (bind
Chad,
Can you provide the output of the test failures, specifically which unit
tests failed and any associated error messages? That would help narrow
down the potential source of the problem.
Regards,
David Handermann
On Mon, Jul 12, 2021 at 9:05 PM Chad Zobrisky wrote:
> Anyone else hav
to have a publicly addressable DNS name, so Let's Encrypt is not an
option in those cases.
Regards,
David Handermann
On Wed, Feb 10, 2021 at 11:09 AM Joe Witt wrote:
> Otto
>
> Installers like you mention are inherently brutal for portability so very
> difficult for us in the comm
concerns with password authentication can be mitigated with one-way TLS, so
a blending of these approaches, as Joe describes in NIFI-8220, seems like a
good way to go.
Regards,
David Handermann
On Wed, Feb 10, 2021 at 8:23 AM Mark Payne wrote:
> I would be in favor of this as well. I ag
Twitter post, this
general discussion is more of a reflection of the need to make things more
secure by default as other products have followed similar approaches.
Regards,
David Handermann
On Wed, Feb 10, 2021 at 8:53 AM Kevin Doran wrote:
> I am in favor of requiring some authenticat
a full understanding of the configuration
required, so it is important to keep the audience in mind when evaluating a
solution.
Regards,
David Handermann
On Wed, Feb 10, 2021 at 7:39 AM Bryan Bende wrote:
> Just to clarify, I was not suggesting that we make a default secure
> setup that re
Mark,
Thanks for clarifying, that makes sense.
Regards,
David Handermann
On Wed, Feb 10, 2021 at 8:41 AM Mark Payne wrote:
> David,
>
> My concern was purely around generating client certs and using mutual TLS.
> I definitely think we should have a server cert if using username
+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.
Configured and tested InvokeHTTP with multiple configurations including
disabling HTTP/2.
Regards,
David Handermann
On Fri, Mar 12, 2021 at 2:19 PM
+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
- Verified Admin Guide update for NIFI-8324
- Verified valid JSON output from SplitJson for NIFI-8342
Regards,
David
On Thu, Mar 18, 2021 at 1:09
timeout setting as the Linux and macOS builds? Introducing one would at
least kill off problematic Windows builds.
Regards,
David Handermann
On Mon, Apr 19, 2021 at 10:08 AM Joe Witt wrote:
> Thanks for bringing this up. The most clear next step I can envision
> at this point is that we br
and project-list command line options
should support building both a module and its dependencies. The list of
changes files can be passed to another action that could determine one or
more modules to build.
Regards,
David Handermann
On Mon, Apr 19, 2021 at 12:56 PM Chris Sampson
wrote:
>
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
> - Depl
is vital to the continued health of the project,
so thanks to everyone who contributes to the testing process!
Regards,
David Handermann
seems like the best use of everyone's time. Thanks for the consideration.
Regards,
David Handermann
On Fri, Aug 27, 2021 at 11:12 AM Mike Thomsen
wrote:
> Some responders seem to prefer a batched migration while others have
> suggested a massive PR that does all of the low-hanging fruit in one
. I would be glad to help with the migration
process, but it would be helpful to avoid having to revisit code multiple
times to address these issues.
Regards,
David Handermann
On Wed, Aug 25, 2021 at 2:24 PM Mike Thomsen wrote:
> I broke up the tickets because it is A LOT of individual ta
Tim,
Thanks for highlighting the updated PR, I provided some feedback and would
be glad to help move it forward.
Regards,
David Handermann
On Fri, Sep 3, 2021 at 5:18 AM Smith, Tim wrote:
> The author submitted a new pull request for ValidateJSON:
> https://github.com/apache/nifi/pul
Thank you all for the congratulations! After using NiFi for several years,
it is great to be able to contribute back. I look forward to continued
involvement on a great project with a great group of collaborators!
Regards,
David Handermann
On Fri, Sep 17, 2021 at 4:25 PM Joe Witt wrote:
>
at
that level, but at least for version 2, maintaining component API
compatibility is key.
Regards,
David Handermann
On Sun, Aug 1, 2021 at 10:23 AM Mark Bean wrote:
> I created a JIRA ticket to investigate and improve the performance of
> InvokeHTTP. It includes a flow definition for benchm
. The existing multi-tenant integration
options cover a wide variety of deployment patterns, but feel free to
highlight potential gaps.
Regards,
David Handermann
On Wed, Sep 29, 2021 at 11:57 AM Michael Radov (RIT Alumni)
wrote:
> Hey,
>
> Hope all is well. Is there a way to have a futur
-sensitive-properties-key
command. If you want to change the algorithm to the new default of
NIFI_PBKDF2_AES_GCM_256, then you can use the encrypt-config.sh toolkit
command described.
Regards,
David Handermann
On Tue, Dec 21, 2021 at 4:43 PM Joe Witt wrote:
> Phil
>
> Not sure if t
- NIFI-9509 Verified successful SFTP retrieval and renaming using AWS
Transfer Family SFTP Server as well as Linux OpenSSH Server
Thanks for the quick turnaround on this release Joe!
Regards,
David Handermann
On Tue, Dec 21, 2021 at 8:19 PM Mark Payne wrote:
> +1 (binding)
>
> Verifi
-1 (binding)
Reproduced the failing system tests described in NIFI-9352. Verified many
other features are working as designed, but I agree that this is a blocker
for the current release candidate version.
Regards,
David Handermann
On Sat, Oct 30, 2021 at 9:26 AM Mark Payne wrote:
>
nning NiFi
container:
docker run --name nifi -p 8443:8443 apache/nifi:1.15.0-dockermaven
If you are still having issues, it would be helpful to provide any logs or
error messages you are seeing.
Regards,
David Handermann
On Thu, Nov 4, 2021 at 8:10 PM Kevin Doran wrote:
> Oh meant t
Verified JoltTransformJSON custom UI works as expected
Thanks for managing the release process Joe!
Regards,
David Handermann
On Thu, Nov 4, 2021 at 6:33 PM Matt Burgess wrote:
> +1 Release this package as nifi-1.15.0
>
> Ran through the release helper and some tests to verify various Jir
Thanks for the update Chris!
I agree with the suggestion to streamline the Dockerfiles for NiFi builds,
there is a lot of duplication between dockermaven and dockerhub, so
unifying the modules and parameterizing necessary differences would be a
helpful improvement.
Regards,
David Handermann
+1 (binding)
- Built nifi-nar-maven-plugin 1.3.3 on Azul Zulu 11.0.10
- Built NiFi using nifi-nar-maven-plugin 1.3.3
- Verified contents of selected extension-manifest.xml files
Thanks for managing the release Bryan!
Regards,
David Handermann
On Thu, Dec 2, 2021 at 8:10 AM Pierre Villard
allow the
OIDC configuration to load as expected in NiFi 1.14.0.
Regards,
David Handermann
On Wed, Dec 8, 2021 at 4:54 AM Ganesh, B (Nokia - IN/Bangalore) <
b.gan...@nokia.com> wrote:
> Hi ,
>
>
>
> We are using apache nifi 1.14 . We have 3 nodes in nifi cluster , cluste
Joe,
Thanks for starting this discussion. Moving forward with a 1.15.1 patch
release sounds like the best path forward.
Regards,
David Handermann
On Mon, Dec 13, 2021 at 7:49 AM Joe Witt wrote:
> Team
>
> We still dont think we are vulnerable but this now highly risky library is
,
David Handermann
On Mon, Dec 13, 2021 at 10:44 AM Chris Sampson
wrote:
> I'd agree. The discussions in Slack and separate user mailing list thread
> are a reassurance for users (who read them), but a patch for the current
> 1.15 branch would seem sensible for people to pick up and as
permits.
https://issues.apache.org/jira/browse/NIFI-8630
Regards,
David Handermann
On Tue, Dec 14, 2021 at 7:52 AM sanjeet rath wrote:
> Hi
>
> The latest 1.15 Nifi version contain mail-1.4.7.jar file(inside
> \lib\bootstrap folder).
> We r using 1.12.1 version of nifi sam
Congratulations Margot!
On Wed, Dec 15, 2021 at 2:50 PM Nathan Gough wrote:
> Congrats Margot, thanks for all your contributions!
>
> On Wed, Dec 15, 2021 at 3:02 PM Chris Sampson
> wrote:
>
> > Congrat Margot!
> >
> > ---
> > *Chris Sampson*
> > IT Consultant
> > chris.samp...@naimuri.com
> >
Thanks for handling this, Matt. As one of the reviewers on the PR, I vote
+1 (non-binding).
Regards,
David Handermann
On Fri, Jul 16, 2021 at 1:20 PM Matt Burgess wrote:
> All,
>
> We've been asked to record our consensus for the move of NiFi Registry
> to the NiFi codebase in a
is better in terms of what should be covered under
the general heading of technical debt reduction.
Regards,
David Handermann
On Fri, Jul 23, 2021 at 12:11 PM Russell Bateman
wrote:
> Bringing up Elastic also reminds me that the Elastic framework has just
> recently transitioned out o
ted and new commits applied
selectively?
Regards,
David Handermann
On Fri, Jul 23, 2021 at 11:29 AM Matt Burgess wrote:
> Along with the itemized list for ancient components we should look at
> updating versions of drivers, SDKs, etc. for external systems such as
> Elasticsearch, Ca
consideration. Many of you have been
developing NiFi for years and I look forward to your feedback. I would be
glad to put together a more formalized recommendation on Confluence and
write up Jira epics if this general approach sounds agreeable to the
community.
Regards,
David Handermann
definitely help with future maintenance.
Regards,
David Handermann
On Sat, Jul 24, 2021 at 10:57 AM Mark Payne wrote:
> There’s also some code that exists in order to maintain backward
> compatibility in the repositories. I would very much like the repositories
> to contain no unneces
documentation includes the contents of the DeprecationNotice for
PostHTTP:
https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.14.0/org.apache.nifi.processors.standard.PostHTTP/index.html
Regards,
David Handermann
On Tue, Jul 27, 2021 at 9:56 AM Mark Bean wrote
it obvious and making
it something that ends up getting ignored.
Regards,
David Handermann
On Tue, Jul 27, 2021 at 10:28 AM Mark Bean wrote:
> I'll start a new thread for PostHTTP when I get a template and/or detailed
> stats.
>
> I know the deprecation is noted in the documenta
properties, upgrading the AWS SDK could be worked independently. Others may
have more insight into particular usage of that library.
Regards,
David Handermann
On Sun, Jul 25, 2021 at 2:12 AM Chris Sampson
wrote:
> Might be worth considering refactoring the build as part of this work too,
> e.g
!
Regards,
David Handermann
On Thu, Jan 13, 2022 at 2:44 PM Joe Witt wrote:
> Hello,
>
> I am pleased to be calling this vote for the source release of Apache
> NiFi 1.15.3.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org
/1.15.2/org.apache.nifi.proxy.StandardProxyConfigurationService/index.html
Regards,
David Handermann
On Thu, Jan 13, 2022 at 12:39 PM sanjeet rath
wrote:
> Hi,
>
> I encounter one "java.net.NoRouteToHostException: No route to host (Host
> unreachable)" in *Nifi UI logi
, then the best approach is to integrate the
ProxyConfigurationService and determine how that should be wired to your
custom component library.
Regards,
David Handermann
On Thu, Jan 13, 2022 at 1:02 PM sanjeet rath wrote:
> Thanks a lot for the quick response.
>
> So u r suggesting we should not
through a proxy server.
Regards,
David Handermann
On Mon, Jan 17, 2022 at 10:07 AM Mark Bean wrote:
> Is anyone else having trouble building NiFi (main) on macOS? I recently
> upgraded to macOS Monterey 12.1 and since then I have not been able to
> build NiFi. I'm not sure if the failur
-1 (binding)
In light of a problem just reported with AccessToken.isExpired()
determination in the StandardOauth2TokenProvider service, this issue should
be corrected:
https://issues.apache.org/jira/browse/NIFI-9801
Regards,
David Handermann
On Wed, Mar 16, 2022 at 12:05 PM Mark Payne 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
to Paul Grey for his efforts to improve the reliability
of the NiFi system tests on GitHub. The resource-constrained GitHub
runners can expose test stability problems that are difficult to track
down, but thanks to Paul's work, the stability of the system tests on
GitHub has improved.
Regards,
David
Mike,
Thanks for reviewing and merging the OAuth2-related pull requests, as well
as the Java 17 build PR! I agree we should be ready to move forward now.
Regards,
David Handermann
On Fri, Mar 18, 2022 at 7:35 AM Mike Thomsen wrote:
> I just finished testing David's patch against one of
a configuration problem, and changing the trust store has a
significant impact on the security profile of the system, this particular
scenario does not seem like a significant concern.
Regards,
David Handermann
On Wed, Mar 9, 2022 at 9:55 AM Joe Witt wrote:
> Mark
>
> The single user a
Hi Steven,
Thanks for your interest! This would also be a great opportunity to
streamline the HTML generation approach to use something like Hugo or
similar static-site generation system.
Regards,
David Handermann
On Wed, Mar 9, 2022 at 12:44 PM Joe Witt wrote:
> Steven
>
&g
Hi Jon,
I just approved the workflow run.
Regards,
David Handermann
On Mon, Mar 21, 2022 at 9:47 AM Jonathan Conti-Vock <
jonathan.contiv...@gmail.com> wrote:
> Hi Devs,
>
> As a first-time code contributor, my pull request [1] requires a maintainer
> to approve runnin
Access Token Provider with Refresh
Window property
Thanks Joe!
Regards,
David Handermann
On Tue, Mar 22, 2022 at 5:50 PM Nathan Gough wrote:
> +1 (non-binding), looks good to me.
>
> Ran through the release helper, tested a few flows, tested a secure cluster
> with external ZK, and
and Spring Boot 2.6.6, which will be incorporated in upcoming
releases.
Please see the following NiFi Jira issue for additional details regarding
the upgrade and background on the vulnerability:
https://issues.apache.org/jira/browse/NIFI-9852
Regards,
David Handermann
On Thu, Mar 31, 2022 at 7
soon, but
it would be helpful for others to give it more attention.
There are a couple other dependency upgrades I plan to put forward soon, so
perhaps waiting until Wednesday would give a bit more time to get some of
those completed.
Regards,
David Handermann
On Mon, Apr 4, 2022 at 3:45 PM Mike
,
David Handermann
On Tue, Jan 25, 2022 at 2:42 AM Isha Lamboo
wrote:
> Hi all,
>
> I hope this question is appropriate for the developers list, if not, I’ll
> move it to users.
>
> I have an Ansible role for NiFi that includes generating the NiFi
> properties files from templa
+1 binding
- Ran build using Node 16.13.2
- Verified hashes and signatures
- Verified License and Notice files
Thanks Scott!
Regards,
David Handermann
On Wed, Jan 26, 2022 at 8:17 AM Shane Ardell
wrote:
> +1 (non-binding).
>
> Performed all verification steps listed in the hel
Updating the minimum Java version in the build configuration would be
helpful, I will look into submitting a pull request to include this check.
Regards,
David Handermann
On Wed, Apr 6, 2022 at 7:23 AM Chakravarty, G wrote:
> Just wondering if Nifi runs through any pre-install checks l
in the build.
Regards,
David Handermann
On Wed, Apr 6, 2022 at 6:16 AM Phil H wrote:
> Australia. Never had any other issues with OpenSSL stuff, etc
>
> On Wed, 6 Apr 2022 at 21:11, Otto Fowler wrote:
>
> > What country are you in? Are you under export controls?
> >
> >
to cached
schemas or inferred schemas used as the basis for customization.
Regards,
David Handermann
On Thu, Apr 7, 2022 at 6:08 AM Edward Armes wrote:
> I've had a quick look in JIRA and it looks like this might have happened as
> a side effect of AVRO-1544.
>
> I think it is wor
Temurin. Any standard
OpenJDK-derived version should work.
Regards,
David Handermann
On Wed, Apr 6, 2022 at 2:31 PM Phil H wrote:
> Much appreciated. If I am upgrading the JDK on this VM (which I will only
> use for NiFi contributions) should I be moving to a more modern version,
> and if
+1
On Thu, Aug 24, 2023 at 10:14 AM Marton Szasz wrote:
>
> +1. I'm not aware of any blockers. Thanks for taking on RM duties.
>
> On Thu, Aug 24, 2023 at 5:04 PM Joe Witt wrote:
> >
> > +1 a lot of nice things in there!
> >
> > On Thu, Aug 24, 2023 at 7:52 AM Martin Zink wrote:
> >
> > > Hi
focused on core capabilities.
Thoughts?
Regards,
David Handermann
[1] https://cert-manager.io
[2] https://github.com/FiloSottile/mkcert
[3]
https://issues.apache.org/jira/issues/?jql=project%20%3D%20NIFI%20AND%20resolution%20%3D%20Unresolved%20AND%20text%20~%20%22TLS%20Toolkit%22
on
physical hardware. With the need to support various approaches,
however, some type of configuration encryption remains a relevant
concern.
Regards,
David Handermann
On Wed, Sep 13, 2023 at 10:19 AM Isha Lamboo
wrote:
>
> Hi David,
>
> My primary use for the TLS toolkit is for lab deploym
for an initial implementation, but it is something I am
planning to evaluate as time allows.
For now, something focused narrowly on FlowFile Version 3 encoding
seems like the best approach.
I recommend referencing this discussion in a new Jira issue and
outlining the general design goals.
Regards,
David
to provide a
bridge while we scope out a rewritten version.
Regards,
David Handermann
On Wed, Sep 13, 2023 at 3:24 PM Joe Witt wrote:
>
> David
>
> Fully supportive.
>
> I'll take it a step further and indicate that I am now an advocate of
> removing anything we have
1.24.0
incorporating additional upgrades, features, and deprecation warnings.
Regards,
David Handermann
On Thu, Oct 12, 2023 at 9:44 PM David Handermann
wrote:
>
> Mike,
>
> Yes that's correct, here's the Jira issue for tracking the migration work:
>
> https://issues.apache.or
of multiple versions, I would
be glad to handle release manager duties for one of the versions.
Regards,
David Handermann
[1] https://issues.apache.org/jira/projects/NIFI/versions/12339599
[2] https://issues.apache.org/jira/projects/NIFI/versions/12353443
forward with an M1 release version.
Regards,
David Handermann
On Tue, Sep 26, 2023, 12:58 PM Joe Witt wrote:
> The Packager thing looks pretty close to being ready anyway. I dont see
> that holding anything up on any line at this point.
>
> I don't have any heartburn waiting for
will be to migrate to the latest version 1 release, and
then upgrade to version 2.
Regards,
David Handermann
On Thu, Oct 12, 2023 at 12:24 PM Mike Thomsen wrote:
>
> When H2 goes, what will the upgrade path look like?
>
> On Tue, Oct 10, 2023 at 7:57 PM David Handermann <
> exception
. There will be some additional work to support migration
on version 1 support branch.
If we want to move forward with a 1.24 release within a week or so,
then these changes could be targeted for 1.25. If we want to wait a
few weeks, then I could see this being incorporated in 1.24.
Regards,
David
Joe,
Thanks for the reply, that sounds good.
For reference, here is the Jira issue for tracking the initial implementation:
https://issues.apache.org/jira/browse/NIFI-12206
Regards,
David Handermann
On Tue, Oct 10, 2023 at 6:53 PM Joe Witt wrote:
>
> David
>
> I think we
Mike,
Yes that's correct, here's the Jira issue for tracking the migration work:
https://issues.apache.org/jira/browse/NIFI-12219
Regards,
David Handermann
On Thu, Oct 12, 2023, 5:29 PM Mike Thomsen wrote:
> This Xodus?
>
> https://github.com/JetBrains/xodus
>
> On Thu, Oct 1
is serious enough that we should release a new patch
version 1.23.2, limited to this particular fix.
I plan to prepare a release candidate build and send out a
short-duration vote thread later today.
Regards,
David Handermann
[1] https://issues.apache.org/jira/browse/NIFI-11971
[2] https
Thanks everyone for the quick replies!
I am starting the release candidate build process and will send a
separate email when the vote is ready.
Regards,
David Handermann
On Mon, Aug 21, 2023 at 10:30 AM Nándor Soma Abonyi
wrote:
>
> +1
>
> > On 2023. Aug 21., at 15:58, D
Team,
NOTE: This is a shortened vote window given the narrow scope of changes.
I am pleased to be calling this vote for the source release of Apache
NiFi 1.23.2.
Please review the following guide for how to verify a release candidate build:
+1 (binding)
On Mon, Aug 21, 2023 at 3:16 PM David Handermann
wrote:
>
> Team,
>
> NOTE: This is a shortened vote window given the narrow scope of changes.
>
> I am pleased to be calling this vote for the source release of Apache
> NiFi 1.23.2.
>
> Please review
Apache NiFi Community,
I am pleased to announce that the 1.23.2 release of Apache NiFi passes:
8 +1 (binding) votes
1 +1 (non-binding) votes
0 0 votes
0 -1 votes
Thanks to all who helped make this release possible!
Here is the vote thread:
The Apache NiFi Team is pleased to announce the release of Apache NiFi 1.23.2.
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.
Java security
policy is highly recommended.
Regards,
David Handermann
On Wed, Aug 23, 2023 at 10:34 AM Martin Fong wrote:
>
> We have an MS SQL connection that worked fine with RH7.
>
> Once we upgraded to RH9 and the crypto policies=DEFAULT
> (https://access.redhat.com/docu
Apache NiFi Community,
I am pleased to announce that the 1.23.1 release of Apache NiFi passes:
5 +1 (binding) votes
6 +1 (non-binding) votes
0 0 votes
0 -1 votes
Thanks to all who helped make this release possible!
Here is the vote thread:
+1 (binding)
On Tue, Aug 15, 2023 at 1:06 PM David Handermann <
exceptionfact...@apache.org> wrote:
> Team,
>
> I am pleased to be calling this vote for the source release of Apache NiFi
> 1.23.1.
>
> Please review the following guide for how to verify a release candid
The Apache NiFi team is pleased to announce the release of Apache NiFi 1.23.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, and
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
- NIFI-9923 Verified component logs contain throwable causes in Bulletin
messages
- NIFI-9954 Verified Spring Framework upgraded to 5.3.19
Thanks Joe!
Regards,
David Handermann
On Mon, Apr 25, 2022 at 1:29 PM Joe Witt wrote:
> Hello,
>
> I am pleased to be calling this vote for t
king issue, in my opinion.
Regards,
David Handermann
On Mon, Apr 25, 2022 at 4:10 PM Mike Thomsen wrote:
> This laptop can be a little wonky at times because of the corporate
> lockdowns, so I wanted to see if any other committers/PMC members have
> seen this in nifi-record-path:
Phil,
Can you provide the version of Maven you are using? Running Maven with the
-X argument for debug will generate a lot of logging information, but it
might point to the POM resolution problem.
Regards,
David Handermann
On Wed, Apr 6, 2022 at 8:13 PM Phil H wrote:
> I reverted back to A
command results, is it possible that your network
connection requires a proxy server?
Running the following OpenSSL command will attempt a socket connection with
TLS to the Maven repository server, to check connectivity:
openssl s_client -host repo1.maven.org -port 443
Regards,
David Handermann
.
The following post provides some additional background on sensitive
properties, as well as the changes introduced in NiFi 1.14.0:
https://exceptionfactory.com/posts/2021/07/29/deciphering-apache-nifi-component-property-encryption/
Regards,
David Handermann
On Wed, May 11, 2022 at 5:07 PM
wrote
Steve,
Thanks for flagging this issue. I commented on the Jira issue after
reproducing the same problem, and I am evaluating a solution.
Regards,
David Handermann
On Thu, Jun 9, 2022 at 12:49 PM Steven Youtsey
wrote:
> When migrating to 1.16.2, we noticed that we lost some parameter cont
, perhaps summarizing the planned implementation in the
Jira issue would be helpful.
Regards,
David Handermann
On Fri, Jun 10, 2022 at 3:06 PM Mike Thomsen wrote:
> https://issues.apache.org/jira/browse/NIFI-9770
>
> Based on David's description saying it will require some deep changes
> to
Severity: high
Description:
The optional ShellUserGroupProvider in Apache NiFi 1.10.0 to 1.16.2 and Apache
NiFi Registry 0.6.0 to 1.16.2 does not neutralize arguments for group
resolution commands, allowing injection of operating system commands on Linux
and macOS platforms.
The
, with the goal of making Java 17 the minimum
before too much time elapses.
As far as a general timeline for removing Java 8 support in NiFi, a good
goal in my mind would be no later than the end of this calendar year, 2022.
Regards,
David Handermann
On Wed, Jun 15, 2022 at 11:55 AM Pierre Villard
wrote
1 - 100 of 267 matches
Mail list logo
