Hi @piyush7829 , I'm assuming you are getting the json {" match_id" : 789456} response from the GetMongo processor, after this you are directly using ReplaceText processor with the replace value: match_id=${match_id:urlEncode()}  This replace value is using flowfile attribute  ${match_id}, but I dont see in your flow where this attribute is defined! I think you are missing a step to extract this attribute between GetMongo & ReplaceText processors. If the response is Json then you can use EvaluateJsonPath processor to extract the match_id attribute : After you connect the "match" rel from the above processor to the ReplaceText processor , the replacement value should work. If that helps please accept solution. Thanks ... View more

@RRG, Not sure I understand. Can you please elaborate? ... View more

@RRG, In the ExtractText you can use the following pattern to get only valid files:   (^((?!README|LICENSE|NOTICE).)*$)   This pattern will exclude any text containing readme, license or notice in it. Hope that helps.   ... View more

Hi @sarithe , I dont think you can achieve what you want using ControlRate processor since this processor is going to allow flowfile to go downstream when MaximumRate is reached besides this processor doesnt support statefulness to control  Max Rate Property over multiple files. Instead I would suggest taking advantage of the UpdateAttribute processor since it supports statefulness over a given attribute. You can use a stateful attribute as a counter that increments\decrements when the flowfiles are being passed through and process accordingly. Then you can check the counter using RouteOnAttribute to see if its less than your threshold (2 in your case) to proceed with processing the flowfiles and if the counter  has reached the threshold, the flowfiles will loop indefinitely until flowfiles being processed are done after which the counter is  decremented. I was able to do that with simple flow to illustrate , but you can use the same pattern to work with your case. The flow I created will do the following: 1- After getting the input, use UpdateAttribute to set the isProcessed flag to 0 2- Use another UpdateAttribute where Store State is set to "Store State Locally". This processor will be used to define rules that will increment\decrement flowfileCounter based on the isProcessed flag as follows:     - isProcessed = 0 and flowfileCounter <  2 then flowfileCounter +=1     - isProcessed = 1 then flowfileCounter-=1  make sure to set the "Stateful Variables Initial Value"  to 0 to initialize your counter. since it starts from 0 then 2ed flowfile will be increment the counter to 1 hence <2 3- Using RouteOnAttribute create two conditional relationship:     - ProcessedRel : check if the isProcessed flag is set to 1 . This basically will route to end of the flow. You can terminate if no farther processing is needed.   - NotProcessedAnd<2 : this will check if the flowfileCounter is less than 2 and flowfile isProcessed is set to 0 to which if true then flowfile will proceed to be processed. If none of the above condition is met, then you can use unmatched rel to loop back to the UpdateAttribute in step 2. 4- Once flowfile are processed use another UpdateAttribute to set the isProcessed flag to 1 and then point the success rel back to UpdateAttribute in step 2 to decrement the counter based on the defined rules. Here how my flow looks like:   GenerateFlowFile: is to simulate creating the input and set the isProcessed flag to 0 on each flowfile (step 1 above) Update flowfileCounter stateful (UpdateAttribute - step2):  used to define the rules for setting the stateful flowfileCounter: click Advanced to define Rules & Actions: Rule1 \ Action 1: Increment flowfileCounter if flowfile not processed and less than threshold Rule2 \ Action 2: decrement flowfileCounter if flowfile is processed   RouteOnAttribute : Proceed if flowfile is not processed and threshold < 2 . Finish if is Processed set to 1, otherwise loop back to step 2 Do Something (ControlRate): this is just to simulate doing something with the flowfiles from the NotProcessedAnd<2 rel above. This where you process the next two flowfiles.   Set isProcessed to 1 (UpdateAttribute -step 4):  set the isProcessed flag to 1 and point the success rel back to UpdateAttribute step 2 to decrement the flowfile counter user Rule2.   If someone think there is a better way please feel free to provide your input. If this helps please accept solution. Thanks     ... View more

Hi @Abhiram-4455 , The easiest way to do such transformation is to use ConvertRecord to convert the format from CSV format to JSON  format, then you can use JoltTransformation processor to do the proper transformation to the final format that you need. To see an example of this please refer to the following post: https://community.cloudera.com/t5/Support-Questions/want-to-convert-csv-to-nested-json-using-nifi/td-p/224954 If that helps please accept solution. Thanks ... View more

Hi @manishg , This has been asked before in a different way but you can implement the same method: https://community.cloudera.com/t5/Support-Questions/Wait-for-a-Flowfile-to-be-picked-only-after-the-previous/m-p/375890#M242696 If that helps please accept solution. Thanks   ... 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