Re: Static processor design

Very well, I have decided to force customer flowfiles through this processor (I did check out the /Listen/* processors, but chose this easier solution). This now works. However, It brings up another question: is this the most efficient way to pass flowfiles straight through this processor

Including total or average queued duration for a Connection within ConnectionStatus

When listing the contents of a connection you can see the queued duration for individual FlowFiles. I believe that could also be a valuable metric to include in the ConnectionStatus that is accessible by reporting tasks as it pertains to the entire connection to give you a sense of how long

Re: Static processor design

*ListenDynamicPropertyChange > On Jan 8, 2021, at 12:42, Otto Fowler wrote: > > So you would be implementing ListDynamicPropertyChange kind of. > > >> On Jan 8, 2021, at 12:41, Otto Fowler > > wrote: >> >> What are the attributes of the processor? >> Do you

Re: Static processor design

So you would be implementing ListDynamicPropertyChange kind of. > On Jan 8, 2021, at 12:41, Otto Fowler wrote: > > What are the attributes of the processor? > Do you have : > > @InputRequirement(InputRequirement.Requirement.INPUT_FORBIDDEN) > or anything? > > You should take a look at the

Re: Static processor design

What are the attributes of the processor? Do you have : @InputRequirement(InputRequirement.Requirement.INPUT_FORBIDDEN) or anything? You should take a look at the Listen** processors. They do not have any inputs etc, and run processing queued input from a background thread. You can have on

Re: Static processor design

I only put the code I want to execute in onTrigger(), I suspected it would not fire there. I know that this isn't what processors do. Configuration is a messy problem to solve when your downstreamers want it made easy. This is supposed to be a solution that allows them to remain in the NiFi UI

Re: Static processor design

Timer Driven/onTrigger (I think) will only fire when an incoming FlowFile is received, thus triggering the processor to execute. But you mention not having any connections (presumably incoming or outgoing), so I guess that's not what you're after? You could try a Scheduling Strategy of "Cron"

Re: Static processor design

Russell, Are you trying to execute the code in onTrigger() only if a dynamic property has been modified? If so you could have a boolean member variable "shouldRun" that gets set to true in onPropertyModified() and checked/reset in onTrigger(). The scripting components do something similar, to

Re: Static processor design

The code I really want to run is sitting in onTrigger(), though I could move it elsewhere. Yes, I have tried *Scheduling Strategy*of Timer driven *Run Schedule*of 10 sec ...but the getLogger().info( "called from onTrigger()" )never reaches /logs/nifi-app.log/ (while the logging statement