In nifi-assembly/target you'll find the built system as you mention, including a "conf" folder that contains (among other things) a file called bootstrap.conf. In that file there's a commented out JVM property to enable attachment by a debugger (the preceding line says "Enable Remote Debugging". When you uncomment that argument and start NiFi, it will listen on port 8000 for a debugger to attach. You can then attach a debugger from your IDE (Eclipse, NetBeans, IntelliJ, etc.). You can change the port and/or set "suspend=y" if you want it to wait until a debugger is attached before continuing startup, the latter is helpful if you are debugging something early in the startup sequence. Otherwise you can wait for NiFi to finish starting up and then attach whenever you like. ... View more

You were so close! By using the [] syntax it just adds to the outgoing array, but you wanted to associate them with the same index, namely the one matched by the * "above" the fields. Put #2 inside your braces (#2 is a reference to the array index you're iterating over, "two levels up" from where you are in the spec): [{     "operation": "shift",     "spec": {       "nummer": "Nummer",       "table": {         "*": {           "zn": "Positionen.[#2].ZeileNr",           "datum": "Positionen.[#2].Datum"         }       }     } }] ... View more

This Chain spec will add the hardcoded value 20190905 into the array (after removing empty values): [   {     "operation": "shift",     "spec": {       "color_*": {         "": "TRASH",         "*": {           "$": "colorsLove[].&2"         }       },       "*": "&"     }   },   {     "operation": "shift",     "spec": {       "colorsLove": {         "*": {           "#20190905": "colorsLove[#2].date",           "*": "colorsLove[#2].&"         }       },       "*": "&"     }   },   {     "operation": "remove",     "spec": {       "TRASH": ""     }   } ] You should be able to replace "#20190905" with a NiFi Expression Language statement, maybe something like: "#${now:toNumber():format('yyyyddMM')}" ... but I didn't try that part. ... View more

If you are not obtaining keys from the database, not using fragmented transactions, and not rolling back on failure, then you should see the failed flow files in a batch being routed to the failure relationship. If you must configure the processor differently, then the flow files will be treated as a single transaction. In that case, in order to handle individual failures you'll want to not use batches, meaning set PutSQL's Batch Size property to 1. ... View more

I don't think your desired output is valid JSON, as the root object only has an array in it, not a key/value pair. If you want a key in there (let's call it root) the following spec will work in JoltTransformJSON: [   {     "operation": "shift",     "spec": {       "*": "root.[]"     }   } ] Otherwise if you just want to add braces around the array, you can use ReplaceText, replacing the entire thing with {$1} ... View more