I dont think there is an out of the box processor where you can utilize such thing. However you can do some workaround where you can use the ExecuteSQL processor instead since this processor allows you to return the stored proc output in Avro format in new flowfile based on whatever your select statement is in the ExecuteSQL SQL Select Query property. Since this will generate new flowfile, the assumption here is that you dont care about the original flowfile.  before going farther and give you an example how to do it, do you want to preserve the original flow file and you were thinking of adding the stored proc output as attribute?   ... View more

Hi @SAMSAL, thanks, i have try this out and it works. I thought you can directly edit the value of the JSON file. Now I have to merge all split JSON files into one again ... View more

Hi, It doesnt seem like "Stuff" function is recognized function through the QueryRecord sql. I think you have two options: 1- If you are dumping this data into a database where you can use the stuff function there then delegate this to SQL before storing\processing the data. 2- Instead of trying to use QueryRecord processor I would try and use the JoltTransformJson with the following spec:     [ { "operation": "modify-overwrite-beta", "spec": { "*": { "tempStart": "=split('', @(1,start_time))", "tempEnd": "=split('', @(1,start_end))", "start_time": "=concat(@(1,tempStart[0]),@(1,tempStart[1]),':',@(1,tempStart[2]),@(1,tempStart[3]))", "start_end": "=concat(@(1,tempEnd[0]),@(1,tempEnd[1]),':',@(1,tempEnd[2]),@(1,tempEnd[3]))" } } }, { "operation": "remove", "spec": { "*": { "temp*": "" } } } ]   Not sure how this will perform with large dataset but its worth testing. Hope that helps, if it does please accept solution. Thanks     ... View more