As you suggested, you can use the JoltTransformJSON processor to "flatten" your JSON, but if your use case is as simple as the provided example (where the fields are one level down), you could also use EvaluateJsonPath with the target set to flowfile-content and the JSONPath expression set to $.Person ... View more

With the ExecuteScript processor, you are likely just adding Dynamic Properties (also known as User-Defined Properties), which are not sensitive. To add your own sensitive properties to a scripted processor, you would need to use InvokeScriptedProcessor. There's an example from the NiFi mailing list (though not with sensitive properties, you'd just need to add .sensitive(true) to your PropertyDescriptor.Builder, and I have another example (with no added properties) on my blog. ... View more

Yes it is possible with ExecuteScript if nothing else. Try the following Groovy script in your ExecuteScript processor: def flowFile = session.get() if(!flowFile) return class WriteCallback implements OutputStreamCallback { Map attrs WriteCallback(attributes) { attrs = attributes } void process(OutputStream outputStream) { outputStream.write('<root>\n'.bytes) attrs.each {k,v -> outputStream.write("<property>\n\t<name>$k</name>\n\t<value>$v</value>\n".bytes) } outputStream.write('</root>'.bytes) } } def wb = new WriteCallback(flowFile.attributes) flowFile = session.write(flowFile, wb) flowFile = session.putAttribute(flowFile, org.apache.nifi.flowfile.attributes.CoreAttributes.MIME_TYPE.key(), 'application/xml') session.transfer(flowFile, REL_SUCCESS) This should pretty-print your attributes in a "properties-style" XML format. Of course you can edit the script to give you the schema you like. ... View more

For CSV files, if you know the number and type of column values, you can use SplitText (to get one row per flow file) followed by ExtractText, supplying a regular expression to get the column values out into flow file attributes. Then you can use ReplaceText to manually enter a SQL INSERT statement (using NiFi Expression Language to access the attributes). For other formats like Avro, as we don't currently have a ConvertAvroToSQL processor, you'd have to convert them for now. Work is underway for a generic system of type conversions, such that you could specify Avro as your input format and perhaps "SQL INSERT" as your output format, thereby effectively making the generic processor work like a ConvertAvroToSQL processor. ... View more