Yep. That’s correct. On Thu, 29 Mar 2018 at 6:45 PM, Jeff Zemerick <[email protected]> wrote:
> Thanks! Just to confirm, each time the processor is started the > @OnScheduled annotated method is executed, right? > > Jeff > > > On Wed, Mar 28, 2018 at 9:07 AM, Sivaprasanna <[email protected]> > wrote: > > > Just to add on top of what Mike said. The @OnScheduled annotation > indicates > > that the method that is marked with this annotation will run when a > > processor is started every time. So basically the setup() will be called > > and executed everytime the processor is started from the UI. > > > > On Wed, 28 Mar 2018 at 6:34 PM, Jeff Zemerick <[email protected]> > > wrote: > > > > > I will give that a go. Thanks for the quick answer, Mike! > > > > > > On Wed, Mar 28, 2018 at 9:01 AM, Mike Thomsen <[email protected]> > > > wrote: > > > > Just do... > > > > > > > > @OnScheduled > > > > public void setup(ProcessContext context) { > > > > //Read properties and do setup. > > > > } > > > > > > > > On Wed, Mar 28, 2018 at 8:57 AM, Jeff Zemerick <[email protected] > > > > > wrote: > > > > > > > >> Hi everyone, > > > >> > > > >> Is there a recommended method for making user-configurable property > > > >> values available to a processor's init()? I would like to load a > large > > > >> index file but allow the user to specify the index's path. I am > > > >> guessing that init() is executed too early to read user properties. > > > >> > > > >> Thanks for any suggestions. > > > >> > > > >> Jeff > > > >> > > > > > >
