Hi @MWM , replacing empty string with null is kind of tricky thing with jolt. Unfortunately there is no direct way that I know of but hopefully my comments will make it easy for you to understand.  Based on your spec I assume you have the following input: { "idTransakcji": "123", "date": "", "name": "sam" } The jolt spec would be like this ( comments start with //): [ { "operation": "shift", "spec": { "idTransakcji": "id", "date": { // Parse date value // if its empty string "" "": { //remove the date from the output "": "user.date" }, //For any values other than "" "*": { //assign the actual value ($) to user.date "$": "user.date" } }, // Assign other fields like name under user "*": "user.&" } }, { "operation": "modify-overwrite-beta", "spec": { "user": { // if the date is found it means that we // should have a value, therefore convert to long "date": "=toLong(@(1,date))" } } }, { "operation": "default", "spec": { "user": { // if the date is not found then set to null // default transformation only works when // the key doesnt exist. "date": null } } } ] You can try the spec here : https://jolt-demo.appspot.com/#inception If that helps please accept solution. Thanks ... View more

Hi @apache_nifi , Its difficult to give you an exact answer without seeing and understanding the whole scenario. For example how those 9 InvokeHttp processors are related and what kind of request body you need to construct for each POST.  If you cant list all the API's and the request body each needs and how are they dependent, maybe you can create an example based on hypothetical situation. However, to give you some direction that might help in your case, there are a lot of processors that you can use in between to help construct the next request body, for example lets say that the first invokeHttp returns a json response and you need some parameters from this response to pass to the next InvokeHttp, then you can use processor like EvaluateJsonPath to get the parameters into flowfile attributes then use ReplaceText processor to replace the json response flowfile content with the new request body and utilize the flowfile attributes you extracted from the json response to populate the needed parameters in the replace value. To demonstrate: Lets assume I want to use Nifi Api to start a processor and run it once , the first invokehttp will be to get the processor information using the processor Id. The response of this invokation will be something like this: { "revision": { "clientId": "value", "version": 0, "lastModifier": "value" }, "id": "value", "uri": "value", "position": {…}, "permissions": {…}, "bulletins": [{…}], "disconnectedNodeAcknowledged": true, "component": {…}, "inputRequirement": "value", "status": {…}, "operatePermissions": {…} }   To change the run state of processor I need to pass the version number alongside the processor id in the request body. To get the version number (0)  from the response above and store it as an attribute I use EvaluateJsonPath like this: Then I use ReplaceText to replace the response content with the run state api request body : In the Search Value I'm using the regex "(?s)(^.*$)" that captures everything and the replacement value is the request body for the next invokehttp: { "revision": { "clientId": "${pipeline.start.processor.id}", "version": ${processorVersion} }, "state": "RUN_ONCE", "disconnectedNodeAcknowledged": true } Notice how I'm utilizing the flowfile attributes using expression language to populate the required parameters like processor id and processor version which I extracted using the EvaluateJsonPath above. Next will will my InvokeHttp passing the new request body content. Hope that helps put you on the right direction. If this helps please accept solution. Thanks           ... View more

My understanding is the file "file.xls" will be uploaded and the file name is stored under filename attribute (make sure to set the file name and extension correctly in the UpdateAttribute as file.xls) , Also make sure the following properties are set as follows: Request Body Enabled : true Request Multipart Form-Data Filename Enabled : true The later will set the Content-Disposition accordingly based on the filename attribute so you dont have to add as dynamic property. Hope that helps.     ... View more

I noticed you are using the "data rate" for the Rate Control Criteria. I dont think this is the correct criteria , instead it should be by "flowfile count". Also you mentioned that you wanted to wait 10 seconds so the Time Duration property should be set as such.   Keep in mind setting the ControlRate this way means , that the processor will allow 1 flowfile to proceed to the success relationship every 10 secs, so if you have 3 files added to the queue around the same time , the first one will proceed after 10 seconds , 2ed will proceed after 20 secs and the 3rd in 30 secs.  If you are looking for only 10 secs on each file , you can use RouteOnAttribute as mentioned here: https://stackoverflow.com/questions/61875809/introduce-time-delay-before-moving-flow-files-to-next-processor-in-nifi   I noticed also from your processors that you are using version 1.18 which should have retryflowfile .   If that helps please accept solution. Thanks ... View more

Hi @Rohit1997jio , What version are you using ? Have you looked into ControlRate processor ( https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.23.2/org.apache.nifi.processors.standard.ControlRate/index.html )? The wait processor is not supposed to be used by itself , it should be accompanied by the Notify processor and its used for certain scenarios where for example if you want to split data into multiple flowfiles and you want to wait for all of them to be processed before performing certain step and so on. If that helps please accept solution. Thanks   ... View more