Thank you, its working with ${anyDelineatedValue("${your_attribute}", ","):equals("US")} ... View more

Thanks @Shu ! It worked, I was using 'Return type' as auto instead of json in EvaluateJsonPath. Thanks for the reply 🙂 ... View more

Thanks @Matt Burgess for clear information. Do you suggest any other approach? I am open for any kind of storage or caching, but end goal is I should be able to use some master data for every flow file validation without impacting performance..... (Master data is combination of company-country-datatype : this i want to use for every flow file validation) Thanks for your response 🙂 Mahendra ... View more

@Mahendra Hegde You can use EvaluateJsonPath processor to extract the value from $.tripSummaryMetaData.orgId then keep as attribute to the flowfile then use RouteOnAttribute processor to check the value of the attribute, 1.If empty then feed to doesn't feed the json message to Jolt transform processor. 2.if not empty then feed the relationship to add the default operation. (or) Use Update Record processor and configure Record Reader/Writer controller services(in writer keep supress null values to true) then using RecordPathvalue, check the value exists for the specific record path by using record path guide, then use If else function to add default value. References regarding UpdateRecord and Record Path Guide ... View more

@Mahendra Hegde Increase the below properties to at least 10,15 secs and try to run the processor again because as you have configured the processor with 3,5 secs now which is pretty low value for timeouts, there is a chance when you are making a call the client probably client is busy with handling other requests and if you are not able to connect to the client with in 3 secs then the request will be routed to NoRetry relation. Connection Timeout 10 secs Max wait time for connection to remote service. Read Timeout 15 secs Max wait time for response from remote service. The flowfile will be transferred to NoRetry relationship when there are 1xx, 3xx, 4xx status codes as you can view the attributes in the flowfiles that routed to NoRetry relation you will have the status code and error that you are getting when the call made to the service. RestApi Error codes: CATEGORY DESCRIPTION 1xx: Informational Communicates transfer protocol-level information. 2xx: Success Indicates that the client’s request was accepted successfully. 3xx: Redirection Indicates that the client must take some additional action in order to complete their request. 4xx: Client Error This category of error status codes points the finger at clients. 5xx: Server Error The server takes responsibility for these error status codes. Please refer to this link for more details about restapi error codes. if you still having issues with the above configs and you are getting responses from invoke http processor after couple of retries then try to increase the values again ,try to make call again. ... View more

Scrabble game is word finder game which is you increase your number and word knowledge. Because its have base of number and words.Then friends boost your knowledge and game skill. ... View more

NiFi does not have a processor that will retrieve a count of the number of files in a source FTP server. You could build in a delay to your MergeContent processor to give sufficient time for all files to be transferred to the NiFi server. Set the "Minimum Number of Entries" to some value larger then you ever expect N to be. Then set "Max Bin Age" to some value (30 mins for example). The age timer starts when the first FlowFile reaches the MergeContent processor. At the configured Max Bin Age, the bin will be forced to merge even if it has not reached the configured Min Num Entries. Thanks, Matt ... View more

Hi @Mahendra Hegde, Please let me know if you have found a solution to the bug as I'm also struggling for the similar reason... ... View more