Hi all,
Let me provide my view to the topic, the development of missing new processors
is relatively easy … and I appreciate focus on performance (Java 21, …),
security and long term sustainability for NiFi v2.
This cleaning (deprecation of obsolete and not secured processors) and product
movement was necessary for future, regards
Ing. Jiri Steuer
(happy to connect LinkedIn<https://www.linkedin.com/in/jiristeuer/>,
Github<https://github.com/george0st>,
StackOverflow<https://stackoverflow.com/users/20266647/jist>)
This item's classification is Internal. It was created by and is in property of
EmbedIT. Do not distribute outside of the organization.
From: maxime.lezier.ik.me via users <users@nifi.apache.org>
Sent: Tuesday, January 28, 2025 9:32 AM
To: users@nifi.apache.org
Subject: [External]Re: Nifi Upgrade - Handling Deprecated Processors
This message is from an EXTERNAL SENDER - be CAUTIOUS, particularly with links
and attachments.
Please report all suspicious e-mails to
helpd...@embedit.com<mailto:helpd...@embedit.com>
________________________________
Hello,
I must admit I have a bit of trouble with this type of response.
For my part, I feel like I'm undergoing this migration to nifi 2.
We've been relying on this tool for most of our workflows for several years (>
40k processors on several platforms) in nifi 1, and the move to 2 looks very
complicated following choices in which the end user doesn't seem to have
weighed much.
I know it's a community-driven tool, and that means accepting its choices.
But as an end-user, all these processor deletions are very difficult to manage,
and to read that it's now up to us to develop everything that's been removed,
when we've been relying on this tool for years, precisely because it natively
embeds all the connectors we need, is very difficult to hear.
Max L.
Le 2025-01-25T23:09:59.000+01:00, Michael via users
<users@nifi.apache.org<mailto:users@nifi.apache.org>> a écrit :
Am 25. Januar 2025 21:11:18 MEZ schrieb Richard Leung
<richile...@gmail.com<mailto:richile...@gmail.com>>:
I'm also interested in knowint as there's a ListenSMTP processor I rely on
that us deprecated and there is no suggested alternative. Thanks!
On Sat, 25 Jan 2025, 12:07 Eren Irmak,
<irmak.e...@gmail.com<mailto:irmak.e...@gmail.com>> wrote:
Hello,
We are upgrading our Nifi and there are thousands of processors in our
flows, many of them are deprecated/erased in 2.1.0.
How do you handle this issue?
Downloading the processor group JSON, changing it manually or
programmatically (defining corresponding new processors in place of the old
ones) and importing to the newer version; could it work ?
Thank you.
Hi Richard,
what about a small SMTP server in a container/pod as your endpoint. E.g.
Postfix and Dovecot. Then, as an alternative to ListenSMTP, a ListenSFTP to
this container, as emails are just plain text files in a defined folder
structure?
Rgds,
Michael
--
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
Envoyé depuis Infomaniak<https://www.infomaniak.com>, email gratuit et
respectueux de la vie privée
