Re: NiFi 1.18.0 Sensitive Property broken after Upgrade

2022-10-14 Thread David Handermann
Josef, You're welcome, and thanks for the understanding reply. I updated the Migration Guidance based on your suggestion, highlighting the issue when upgrading from 1.15.3 and earlier to 1.17.0 or 1.18.0. I am also tracking the SFTP issue described in NIFI-9989. This issue is resolved in the

Re: DistributedMapCacheServer persistent directory - Cluster wide same values after primary node changes

2022-10-14 Thread Chris Sampson
The DistributedMapCacheServer is, I believe, meant as a reference implementation of the service to be used as an example rather than in production. The kind of scenario you describe is exactly the reason to not use this in-memory (optionally locally persisted on disk) in a clustered production

DistributedMapCacheServer persistent directory - Cluster wide same values after primary node changes

2022-10-14 Thread Jörg Hammerbacher
Hi, I have one thing where i am looking for a solution. Maybe someone can help me out or give me hint how to do. Problem: I often use a NiFi Clusters with "DistributedMapCacheClientService" which uses a "DistributedMapCacheServer" for cluster wide key/value storage. Per default the DMCS

Re: NiFi 1.18.0 Sensitive Property broken after Upgrade

2022-10-14 Thread Josef.Zahner1
Thank you guys for fixing it and for providing the workaround. We searched in the release notes for any hints regarding the migration from 1.15.3 to 1.18.0 and found nothing, may be a short notice would be great that a upgrade from <.1.16.0 to 1.17.0/1.18.0 could brake some of the sensitive