Re: Make NiFi Flow Read Only on Disconnect

2021-08-26 Thread Mark Payne
Bryan, Those changes only affect when a node starts up, not when it reconnects to a cluster after startup. However, there is a Jira [1] that I’m working on currently that should facilitate this approach. Thanks -Mark [1] https://issues.apache.org/jira/browse/NIFI-9069 > On Aug 26, 2021, at

Re: Make NiFi Flow Read Only on Disconnect

2021-08-26 Thread Joe Witt
Shawn Ok cool. I think we'll go that route. A lot less code. A lot easier to reason over. We tried to be clever and it kept backfiring. Simpler wins. Thanks On Thu, Aug 26, 2021 at 8:28 AM Shawn Weeks wrote: > > As long as we have a check to make sure no data is in flow on the node >

RE: Make NiFi Flow Read Only on Disconnect

2021-08-26 Thread Shawn Weeks
As long as we have a check to make sure no data is in flow on the node joining that sounds wonderful and a lot simpler. In my most recent case I just stopped the inputs and waited till everything cleared and then shutdown and delete flow.xml.gz and restarted. That's already worlds easier than

Re: Make NiFi Flow Read Only on Disconnect

2021-08-26 Thread Joe Witt
Shawn So that is one direction (being more restrictive). Another direction is to simply ditch the logic we have and allow changes and simply update the disconnected node when it rejoins. We have all kinds of super complex super duper awesome logic in there to help prevent users from getting

Handling floating point numbers

2021-08-26 Thread Vibhath Ileperuma
Hi All, I have created a Nifi flow to query from Postgresql database and write data into csv files. However, I noticed that the floating point values (Double values) can be changed slightly when writing to csv files. For an example, value 4313681553.3 was written as 4313681553.292. Since some

Make NiFi Flow Read Only on Disconnect

2021-08-26 Thread Shawn Weeks
Hi, I know there have been a lot of improvements handling flow.xml.gz differences between nodes if a node get's disconnected or is down. I was wondering if there is a way to prevent NiFi from allowing any flow changes if all nodes are not up and available, both on the node that's in a