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

If you are trying to add an attribute to a flow file, you can use UpdateAttribute for that. If you are trying to add a property to a processor, then it depends on the processor whether it supports dynamic (or "User-Defined") properties. If a processor does not support dynamic properties, then when you try to add one, the processor will be deemed invalid. ... View more

QueryDatabaseTable is usually used for "incremental" fetching, meaning it will only grab "new" rows. This is based on the "Maximum Value Columns" property, which is usually set to an ID or timestamp field in the database. That is what allows the processor to only grab "new" rows, as it will keep track of the maximum value it has seen so far for the column, and the next time it runs, it will fetch only those rows whose value is greater than the last max it saw. If you are not setting a Maximum-Value Column, then QueryDatabaseTable acts much like ExecuteSQL, in the sense that it will keep repeating the same query and thus give duplicate rows. So for your use case I recommend setting a Maximum Value Column for that processor. If there is no such field in the table, then you're really looking at more of a "run-once" scenario, which is not currently supported. ... View more