Hi @araujo , Thanks for the uploaded docker-compose.yml.  I have tried the steps in the here, but the command "docker-compose up -d" failed on the proxy container due to the fact that ./nginx.conf should have been a file. Would you elaborate the volumes setting for the proxy?  The proxy container in question taken from your repo is excerpted below.  proxy: image: nginx:latest container_name: proxy # volumes: # - ./nginx.conf:/etc/nginx/nginx.conf:ro ports: - "8443:8443" networks: - nifi depends_on: - nifi0 - nifi1 Secondly, I need your help because after I brought up all containers with two line commented out above I cannot access this two-nodes NiFi cluster with the curl command below $ curl -v https://localhost:8443/nifi * Trying 127.0.0.1:8443... * Connected to localhost (127.0.0.1) port 8443 (#0) * ALPN, offering h2 * ALPN, offering http/1.1 * CAfile: /etc/ssl/certs/ca-certificates.crt * CApath: /etc/ssl/certs * TLSv1.0 (OUT), TLS header, Certificate Status (22): * TLSv1.3 (OUT), TLS handshake, Client hello (1): * TLSv1.0 (OUT), TLS header, Unknown (21): * TLSv1.3 (OUT), TLS alert, decode error (562): * error:0A000126:SSL routines::unexpected eof while reading * Closing connection 0 curl: (35) error:0A000126:SSL routines::unexpected eof while reading Thanks, David ... View more

I dont think you can use PutSQL for this. Try ExecuteSQL or you might have to use ExecuteScript processor as other posts suggest: https://community.cloudera.com/t5/Support-Questions/Does-ExecuteSQL-processor-allow-to-execute-stored-procedure/m-p/158922 https://stackoverflow.com/questions/72348844/get-output-of-stored-procedure-using-putsql-in-nifi If that helps please accept solution. Thanks ... View more

Thank you so much too. This also works. But i am actually a learner using Jolt. ... View more

Thank you sir @SAMSAL . I am very grateful, at the moment, your solution does the job. Also, i would love to learn JoltTransformation from you. Thanks once again. ... View more

@udayAle @ep_gunner  When NiFi is brought down, the current state (stopped, started, enabled, disabled) of all components is retained and on startup that same state is set on the components.  Only time this is not true is when the property "nifi.flowcontroller.autoResumeState" is set to false in the nifi.properties file.  When set to false a restart of NiFi would result in all components in a stopped state.  In a production environment, this property should be set to true.  Perhaps you can share more details on the maintenance process you are using as I am not clear on how your maintenance is impacting the last known state of some components. If you found that the provided solution(s) assisted you with your query, please take a moment to login and click Accept as Solution below each response that helped. Thank you, Matt ... View more

As @SAMSAL pointed out, queryrecord is the best and easiest method to use. Here, i have created a sample flow for your use as pix attached. I hope it helps. ... View more

Thank you all. I eventually evaluated the json path to extract the url. My mind was astray as i was using complex solution to a simple problem.  ... View more

@rafy  The ERROR shared seems unrelated to the action of emptying a connection queue. Are you trying to delete a connection or empty a connection queue? Can you share screenshots of the actions being performed? Can you collect the full stack trace produced in the nifi-app.log when you perform the action? Thank you, Matt ... View more