NIFI-3413 describes a GetChangeDataCapture processor, which will generate events that correspond to database updates (rows added, tables changed, e.g.). The hope is that it will support MySQL, Oracle, and SQL Server (although the first release of the processor may not). Development of the MySQL CDC support (via its binlog files) is underway. ... View more

To put each of the ServiceCodes values into its own "row", you can use JoltTransformJSON with the following shift specification: { "operation": "shift", "spec": { "ServiceCodes": { "*": { "@(2,Time)": "[&].Time", "@(2,Subscription)": "[&].Subscription", "@": "[&].ServiceCode" } } } } Given your input above, it will produce the following: [ { "ServiceCode" : "SERVICE_CODE1", "Subscription" : "1234567", "Time" : "03/07/2017 11:45:46.365" }, { "ServiceCode" : "SERVICE_CODE2", "Subscription" : "1234567", "Time" : "03/07/2017 11:45:46.365" }, { "ServiceCode" : "SERVICE_CODE3", "Subscription" : "1234567", "Time" : "03/07/2017 11:45:46.365" }, { "ServiceCode" : "SERVICE_CODE4", "Subscription" : "1234567", "Time" : "03/07/2017 11:45:46.365" } ] This might be able to go directly into ConvertJSONToSQL, but if it doesn't, you can use SplitJSON with $[*] or $.* as the JSON Path expression, and it will divide the array up into one flow file per object in the array. Then you should be able to transform it to SQL. ... View more

If your configuration of ExecuteStreamCommand outputs an integer and you would like it in an attribute, try setting the "Output Destination Attribute" property of ExecuteStreamCommand to the attribute name you'd like, and use the "original" relationship to transfer the flow file downstream. That will give you a flow file with the same incoming content as well as an attribute whose name is of your choosing and whose value is the output stream returned (hopefully the same value you mention your command returns) by the command you are executing. If instead you want the exit code of the command, you will find it in the "execution.status" attribute of the outgoing flow file (see doc here). ... View more

All Property Descriptors (required or optional) must have a Validator set explicitly, otherwise it will return the error you are seeing. It appears you are not looking to perform validation, but you still must set a validator, so on your optional properties add the following to the builder: .addValidator(Validator.VALID) ... View more