@Krishna Sreenivas As of now there is no built in processor in NiFi that could extract Json attribute dynamically because if we add significant number of attributes dynamically to the flow file, As attributes are hold in memory this will cause performance issues. We need to add all the json keys/attributes and matching json path as value in EvaluateJsonPath processor and change the destination property to flowfile-attribute to keep them as a flow file attributes. Please refer to This link for more details regarding dynamic attribute extract processor. Refer to this link regards to similar kind of usecase and end of this thread there is script which you can leverage to extract key/values. - If the Answer helped to resolve your issue, Click on Accept button below to accept the answer, That would be great help to Community users to find solution quickly for these kind of issues. ... View more

@Mitthu Wagh Use getDelimitedField function and use UpdateAttribute processor and add new properties like. a ${fileName::getDelimitedField(1,'_')} b ${fileName::getDelimitedField(2,'_')} By using getDelimitedField function we are going to add all the attributes you needed. - If the Answer helped to resolve your issue, Click on Accept button below to accept the answer, That would be great help to Community users to find solution quickly for these kind of issues. ... View more

@yazeed salem Method1:Using UpdateAttribute+RouteOnAttribute Processors it would be easier if you introduce new update attribute processor before RouteOnAttribute and prepare two new attributes in UpdateAttribute processor. Configs: Then in RouteOnAttribute processor use or function to Configs: Now processor will route the flowfile to ROUTE1 relationship. (or) Method2: By using RouteOnAttribute processor: Use the below expression in ROUTE1 property value ROUTE1 ${literal(${text.tag.type:equals('XXX'):and(${txt:contains('YES')})}):or(${text.tag.type:equals('YYY'):and(${txt:contains('NO')})})} Both Methods will result the flowfile into ROUTE1 relationship, Choose the method which best for your case. - If the Answer helped to resolve your issue, Click on Accept button below to accept the answer, That would be great help to Community users to find solution quickly for these kind of issues. ... View more

@Mark I tried your case By using UpdateAttribute's Store the state feature. flow: 1.Two GenerateFlowfiles //to get 2 flowfiles2.SplitText //split the flowfile into 1 line 3.ExtractText //extract the first value of the from the content 4.RouteOnAttribute //check the extracted value from the flowfile attribute 5.UpdateAttribute //add one to the seq attribute and reset the seq attribute value when it reaches to 10(advance d usage of update attribute processor) 6.RouteOnAttribute //check seq attribute value and send to putemail if seq = 10 7.PutEmail //send mail I have attached flow template, reuse it and change as per your requirements. 222030-support-update-reset.xml ... View more

@Raj ji For this use case you have to use Wait-Notify processors to finish inserting records first then Update the records and last for deleting the records. Refer to this and this articles for configuring and usage of Wait/Notify processors. ... View more