@GMAN  Here is my try to help you further. flow   Look at the picture of the InvokeHTTP. InvokeHTTP From my experience most options can mostly be left to default values. Your Json-body should be fine and will be send with the request. Remarks: - Authenticaton/Authorization: You have to try the two possibilities I know. For the second you have to add custom-property "Authorization" with the plus symbol on the right above. - Accept: Concerns the response format not sure wether you will need this.   Maybe you can first build your request in Postman and after successfull execution then click to "code" -> "HTTP". There you can see the details needed for the request.   In the "Settings" of the InvokeHTTP you can autoterminate the "original" flowfile. For "Retry" you can use the shown processor with default values. All "Failure" or "No retry" go to some error-handling. With "Response" you can go further in your flow.   Hope this helps you to come forward. ... View more

@adhishankarit    Sadly I have no experience doing such kind of logging in own files to a NFS.   But what about logging to nifi-app.log? I don't understand the problem you mentioned in your first post concerning this. Using the LogAttribute-processor gives you some options (attributes, content) what and how to log there. With the option "Log prefix" you can evaluate data by this value later. IMHO Logging all attributes would be advantage because not all processors deliver the same attributes after they ran.   Maybe you can do something with scripts like mentioned here: https://community.cloudera.com/t5/Support-Questions/Is-possible-to-write-an-attribute-into-a-file-and-also-keep/td-p/184414   Sorry but im neither fit with scripting nor with this kind of logging so I'm not able to help you further. But maybe some other guys here will help you. ... View more

@stephane_davy  Sorry I couldn't work on this further last week. Now my solution looks like this.   JSON from GenerateFlowFile [ { "myfield": "JustForHavingJson", "myfield1": "A" }, { "myfield": "JustForHavingJson", "myfield1": "B" }, { "myfield": "JustForHavingJson", "myfield1": "C" }, { "myfield": "JustForHavingJson", "myfield1": "D" }, { "myfield": "JustForHavingJson", "myfield1": "E" }, { "myfield": "JustForHavingJson", "myfield1": "X" }, { "myfield": "JustForHavingJson", "myfield1": "" } ]   Definitions of ControllerServices and AvroSchemaRegistry ControllerServices and AvroSchemaRegistry Flow Flow   Details of RecordProcessing-Processors Details RecordProcessing-Processors   Result FF-Content after MergeRecord: {"myfield":"JustForHavingJson","myfield1":"A","myfield2":"C"} {"myfield":"JustForHavingJson","myfield1":"B","myfield2":"C"} {"myfield":"JustForHavingJson","myfield1":"C","myfield2":""} {"myfield":"JustForHavingJson","myfield1":"E","myfield2":""} {"myfield":"JustForHavingJson","myfield1":"X","myfield2":""} {"myfield":"JustForHavingJson","myfield1":"","myfield2":""} {"myfield":"JustForHavingJson","myfield1":"D","myfield2":"G"} Personally I wouldn't do a MergeRecord at the end but go on with the three single connections of the UpdateRecord processors.   Do you think this could be a possible solution or have you found a better way to do this? ... View more

@ang_coder  The AvroSchemaRegistry is to set in the ControllerServices. If it should be available in your whole NiFi just go to the canvas and click anywhere right -> choose "Configure". It is the same place where you define your database connections. Configure -> ControllerServices If you already have JSON-format just ignore the first two steps of my example flow where data were retrieved and converted to JSON. Start with your JSON at UpdateAttribute which doesn't care about the kind of flowfile content. The ConvertRecord in my example uses an JSON-reader and JSON-writer where the writer points to the AvroSchemaRegistry with the schema.name set in UpdateAttribute. Therefore the JsonRecordSetWriter_IJ_TestMoreColumnsAtTarget (just to take a short name) has the specification "Schema Access Strategy" with option "Use Schema.Name Property". Have a look at the configuration details in my post before. Hope this helps. ... View more

@dzbeda  Try it with:  /*:Event/*:System/*:Channel ... View more

@ang_coder   Tried it myself and have to correct my idea a little bit. Have a look at my example. Here are my tables. The target table has two columns more than the source. Tables I defined following ControllerServices: ControllerServices And created this flow: Flow Here the information of the single processors: Processor information In my example it works. Sure there will be a more elegant solution but I don't know how. ... View more