Hi @mohdriyaz , I dont think you can accomplish this using the UpdateRecord processor as the added property has to be valid record path where the fields are specified explicitly. I can think of two options to do this:   1- Using JoltTransformJson:  you can use "modify-overwrite-beta" spec to update a field but since the spec allows expression language and flowfile attribute evaluation you can reference the field name in the spec dynamically. In this case the spec will look like this: [ { "operation": "modify-overwrite-beta", "spec": { "${col_name}":"9999" } } ]   2-Using  ExecuteScript: You can write custom script like groovy, python ...etc.  (depending on what Nifi version you are using) the script will basically read the json content into some dictionary or hashmap structure, read the flowfile attribute "col_name" into a variable and use that variable as a key to the field that you need to change in the json dictionary. Finally write then new content to the flowfile and pass to the success relationship. You can do error handling there as well and send any errors to the failure relationship.  For more info on how to update flowfile content using ExecuteScript processor please refer to the "Reading and writing to/from a flow file" section under this link:  https://community.cloudera.com/t5/Community-Articles/ExecuteScript-Cookbook-part-2/ta-p/249018 If you find this is helpful please accept solution. Thanks   ... View more

Hi, You can do this in different ways , here is one of them: [ { "operation": "shift", "spec": { "@uniqueIdentifier": "_id", "*": "&" } } ] Hope that helps.   ... View more

Actually there is a property called "Move Destination Directory" : As the description says on this properties: "this property is ignored unless the Completion Strategy is set to Move".  The same rule applies on the Move Conflict Strategy as its only considered when the Completion Strategy is set to Move . If your Completion Strategy is set to None or Delete then both properties will be ignored. ... View more

Ok, I think I know what you mean now.  Basically the GetFile is designed not to take any incoming connection as you can see in the processor documentation: The reason  such restriction applies depend on how the processor works. The GetFile is designed as a trigger processor and it executes every time a file is placed in the target path, so providing an incoming relationship (wither through routeOnAttribute or any other processor) will break this rule because that means the GetFile will only work and Get the file when upper stream processor triggers that via sending flowfile which is not what this processor is designed to do. What you need is FetchFile processor given that you know the file you are looking for because this processor takes the full file path and not just a directory.   ... View more