@Ghilani You should know these 3 articles intimately if you want to use Execute Script   https://community.cloudera.com/t5/Community-Articles/ExecuteScript-Cookbook-part-1/ta-p/248922 https://community.cloudera.com/t5/Community-Articles/ExecuteScript-Cookbook-part-2/ta-p/249018 https://community.cloudera.com/t5/Community-Articles/ExecuteScript-Cookbook-part-3/ta-p/249148     That said, it's sometimes helpful for me to see a working example and modify from there.  As such, here is a github with a sample flow definition file (01_Fraud_Detection_Demo_Params_ExecuteScript.json) and script file(Fraud Demo ExecuteScript.py) that should work out of the box:   https://github.com/cldr-steven-matison/Fraud-Prevention-With-Cloudera-SSB/tree/main/Templates   Pay attention to imports and, then line 160 is what you want to get the flowfile.   My flow ignores the content, but you should be able to find references in the Part 1 cookbook for anything you want to do w/ flowfile content.           ... View more

@madhs @joseomjr A great example of the configuration is above.   Here is a full flow definition file/example showing how to get values from JSON and prepare ahead of an InvokeHTTP processor:     Flow Def File: https://raw.githubusercontent.com/cldr-steven-matison/NiFi-Templates/main/InvokeHttp_Demo_2.json ... View more

@bhadraka Check out this flow definition example for how to prepare and test JSON ahead of an invokeHttp post.   Flow Def File: https://raw.githubusercontent.com/cldr-steven-matison/NiFi-Templates/main/InvokeHttp_Demo_2.json     As far as the post itself goes.  I highly recommend that you test API calls with something like Postman so that you can clearly test what headers and such are required so that the API call works.  Only then try to make it work with InvokeHttp duplicating all headers.     Figuring out how to get the call to work and how to configure InvokeHTTP at same time is not fun. TIP:  in Invoke HTTP click the + to add key value pairs corresponding to your headers or values you need to pass.     ... View more

@Juanes I believe you just need to resolve the missing dependency.    Check out this solution: > pip3 install python-setuptools > yum install impala-shell https://community.cloudera.com/t5/Support-Questions/How-to-install-impala-shell-on-RHEL-8-3-to-communicate-with/m-p/313665   ... View more

@Manimaran Wait/Notify should be able to do what you are describing in the deeper dialouge.   Based on your current flow complexity,  I would recommend that you build a new sample to learn how wait/notify behavior works in nifi.   This is very difficult setup, so having a learning flow w/o context of the existing functionality is highly optimal.   Then you can refactor your sql flow accordingly, without having to figure out how to get wait/notify working during that refactor. ... View more

@DTM In that case you would need to use the DatabaseConnectionPool and jdbc to aws postgres.  This will require permissions to allow nifi network to speak to RDS endpoint.  If you cant use DBCP,  you will have to put something between the RDS and nifi.  For example nifi could use invokeHTTP to send/post data to an ec2 instance with some kind of API that can do the connectivity. ... View more

@DTM You are correct, to use an AWS credentials in nifi, you need to use the Controller Service.   This controller service is then referenced by processors as a drop down menu for AWS Credentials Provider Service.  If one does not exist in the drop down you can chose to create it.   https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-aws-nar/1.21.0/org.apache.nifi.processors.aws.credentials.provider.service.AWSCredentialsProviderControllerService/index.html   An example of one such processor is GetDynamoDB but there are many.  Just search AWS in the processor search box to find all aws related processors. ... View more