Hello! An "event" in the context of the NiFi @EventDriven annotation is the arrival of a flow file in the queue that is an input to a processor. The only purpose of @EventDriven is to save system resources when compared to the default Timer Driven strategy, in which a processor polls its input queues for flow files to work on.
If this matches your expectation for the Event Driven scheduling strategy, then you must generate an "event" with another processor on the NiFi graph. This could be as simple as a GenerateFlowFile processor that runs on a predictable Timer Driven period or Cron Driven schedule. You could also use another ingress [1], or data ingestion processor [2], to create a new flow file containing an event. [1] - http://nifi.apache.org/docs/nifi-docs/html/developer-guide.html#ingress [2] - http://nifi.apache.org/docs/nifi-docs/html/getting-started.html#data-ingestion I hope this helps, -- Mike On Wed, Dec 27, 2017 at 10:34 AM, Milan Das <[email protected]> wrote: > I am trying to build a custom processor with “Event Driven”. I added > “@EventDriven” annotation. It is showing EventDriven in the scheduling > strategy. > > Question: how to send an event to this processor to intiate the flow? What > are my options? > > > > Regards, > > > > [image: graph] > > *Milan Das* > Sr. System Architect > > email: [email protected] > > [image: dIn icon] <https://www.linkedin.com/in/milandas/> > > www.interset.com > > > > > > >
