I am not aware of any bulk update capability through the UI. At a glance I did not see this option yet via the API, so the following may be a reasonable workaround (disclaimer: I did not try something like this myself):   1. Export the process group in which you want to update all the queues (perhaps manually update 1 connection to see what it looks like) 2. Write a script to update all the connections in the template   This would still involve manual steps, but if you have a few groups with 100 queues it could save a lot of time. Also, don't hesitate to share if this indeed worked out. ... View more

@Rohitravi  The None of NiFi's processors will release any FlowFiles to a downstream connection until the end of the thread operation.  This is to protect users from dataloss and in some cases data duplication in the result of a failure. In the case of a SplitText processor you have configured to split on every 10 lines.  The processor will stream the content of the first 10 lines in to a content claim in the content_repository and create a new FlowFile record pointing at that claim.  The next 10 lines may or may not go into that same content claim and another FlowFile record is created. above process continues until all splits have been created.  Then The processor releases all FlowFile created to the downstream connection at the same time. NiFi does not guarantee FlowFile processing order. You can adding the FirstInFirstOutPrioritizer to the downstream connections to help with ordering some. Hope this helps, Matt ... View more

Thanks a lot Matt!! ... View more