Hello @gari A NiFi processor will only read in a FlowFile from an inbound connection when it executes, which means the processor has no access to a FlowFiles attributes until it executes. This makes it impossible for a processor to use a FlowFile's attributes to set when the processor should execute. You can only use NiFi Expression Language (EL) in component configuration properties that support EL. None of the configuration setting on the "Settings" or "Scheduling" tabs of a component will support EL. Also be careful using a "match" type rule in your routeOnAttribute processor dataflow. What happens if a GC event or threading issue slows down the reprocess loop and the exact "matching' time is missed. The FlowFile would forever be stuck in the loop. Maybe consider using a "Less than or equal to" (le) function instead. FlowFile Attributes live in heap memory, so executions performed by your RouteOnAttribute processor should amount to very little actual CPU usage. Are you observing a large "time" per 5 minute stat on the processor? Perhaps adjust the run schedule to on the RouteOnAttribute processor to control how often it checks inbound FlowFiles. "0 sec" means run as fast as the hardware will allow. Try changing to ".5 sec" to reduce some of the usage. Hope this helps, Matt
... View more
I am trying to bulk insert my csv file to mysql table using PutDatabaseRecord.
My CSV file contains all the column values except for the last column as it is auto incremented in table in case of insertion.
Can you help me with the attribute setting or processor setting in that case?
... View more