Hi @anarasimham Thank you very much for your answer. It answers most of my questions! A couple of questions are still not clear to me. 1. Data loss during flow redeployment. You mentioned how is data buffered in queue between two processors during processor updating/stopped. How does the workflow as a whole redeployment(stopped/updating) affect data loss? For example, I am running a flow f1 in NiFi. I am going to deploy f2 to replace f1 for the same input source and business logic. f2 has a few more processors than f1. So I undeploy(stop and delete) f1, then deploy f2. There is a time window between f1 is stopped and f2 is started. Since the data is streaming in, and there is no queue as buffer(the entire flow is stopped), how do I avoid data loss? Or maybe this is not the right way to do workflow updating? BTW, we are not supposed to click buttons on WebUI in production. I understand it is much easier to work with flow update on Web UI in production. But we can't directly change flows in production. We have to make flow changes in Dev env and test it. Then, deploy the new flow via CI/CD in an automated way by using NiFi REST API or tools. 2. Authorization and Access Policy You mentioned Apache Ranger to work with NiFi on authorization. I noticed there are some conf files: authorizers.xml, authorizations.xml, users.xml for authorization setup. Is it enough for production? Do we have to use Apache Ranger since this introduces one more service in our platform? Thanks.
... View more
