Hi, Please try the following spec: [ { "operation": "shift", "spec": { "timestamp": { "*": { "@(2,resourceid)": "[&1].resourceid", "@": "[&1].timestamp" } }, "Key": { "*": { "@": "[&1].key" } }, "data": { "*": { "@": "[&1].data" } } } } ] If you find this helpful, please accept solution. Thanks ... View more

Hi, Is your input in Json format? if its json do you need to completely replace it with the output you specified? If that is the case then you dont need Jolt transformation, instead you can do the following: 1- Place the Gallery_Ids attribute as flowfile content. You can do that using the ReplaceText processor where the Replacement Value is the attribute ${GALLERY_IDS} 2- Do SplitJson to split the Array into a different flow file, this should give 7 flowfiles with the values: 1,2,3,4,5,6 & 7 3- Add another ReplaceText processor that will capture each split from above and replace the flowfile content with the following template in the Replacement Value: {"GALLERY_ID":"$1","PERSON_ID":"test$1"} Leave the Search Value as (?s)(^.*$) This should again give you 7 flowfiles with the expected output format.   Hope that helps, if it does please accept solution. Thanks ... View more

hmmm, you are right! the ValidateXML processor only accepts variables from the variable registry as noted in the Schema File property description. @MattWho , @araujo do you know why is this the case for the ValidateXML and what would be the proper solution? The only way I can think of in this case is updating the variable in the variable registry through the API to assign the proper value to the schema.name variable: https://stackoverflow.cm/questions/52010827/how-to-change-nifi-variable-registry-using-rest-api   ... View more

Hi,   To answer your question, it depends: 1- If the attribute value that on the xml flowfile can be used to derive the XSD file name\path then you can use Expression Language to construct the XSD file name from the attribute value when assigning the "Schema File" property. For example if all XSD have the following filename format [SomeID]_XSD_File.xsd and the attribute "Id_Attribute" has the ID then the "Schema File" property can be set to: ${Id_attribute:append('_XSD_File.xsd ')}   2- If the xsd file name cant be derived through the attribute value and you have to do some If-Else conditions based on the attribute then you can use ExecuteScript processor do that and set new flowfile attribute with the xsd file schema path. To learn how to use the ExecuteScript to add new attribute based on some custom code you can check the "Recipe: Add an attribute to a flow file" under: https://community.cloudera.com/t5/Community-Articles/ExecuteScript-Cookbook-part-1/ta-p/248922   3- If you dont want to use ExecuteScript processor, you can utilize the UpdateAttribute Processor by creating different Rules, Conditions & Actions to set a File Schema attribute that can be used in the ValidateXML File Schema property. To learn how you can create different rules , condition & action please check the following tutorial: https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-update-attribute-nar/1.5.0/org.apache.nifi.processors.attributes.UpdateAttribute/additionalDetails.html   Hope that helps, if it does please accept solution. Thanks   ... View more

Hi, I'm not sure if you can use Regex in jolt transformation,  but you can use wildcard (*) instead. Keep in mind even with Regex you still need to find the common denominator for each attribute to be able to match, so wildcard should suffice. To use the wildcard you can apply something like this to your spec:   [ { "operation": "shift", "spec": { "my_id": "my_id", "my*company*sa": "my_company_sa", "*RH": "my_company_rh" } } ]  Hope that helps, if it does please accept solution. Thanks ... View more