@stevenmatison    I still haven't had any luck with this at all. Do you know if an error on one specific file could cause the entire process to crash and not complete or does it attempt to skip over bad files? ... View more

Great, thanks a lot ... View more

@vikrant_kumar24  - Have you found a better way to solve this ? If so would be curious to hear that! ... View more

hi @nshawa, I am having the following error on PutHiveStreaming processor after running the template you provided:   Any idea how to fix this? ... View more

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