Re: [NIFI-CPP] Issues with TIMER_DRIVEN and CRON_DRIVEN

I wanted to follow up and say that timer driven and event driven are the only scheduling strategies available in minifi c++. Cron is not a supported strategy yet. Sorry for not mentioning this earlier On Sun, Apr 22, 2018, 4:05 PM Iyán Méndez Veiga wrote: > Hi, > > I haven't

Re: [NIFI-CPP] Issues with TIMER_DRIVEN and CRON_DRIVEN

Iyán, Is there an error or session rollback in the log file? You can view issues here: https://issues.apache.org/jira/projects/MINIFICPP/issues Thanks, Marc On Sun, Apr 22, 2018 at 4:05 PM, Iyán Méndez Veiga wrote: > Hi, > > I haven't been able to configure

[NIFI-CPP] Issues with TIMER_DRIVEN and CRON_DRIVEN

Hi, I haven't been able to configure MiNiFi to take pictures every 30 seconds using GetUSBCamera processor. I have the following in the config.yml - name: take_picture class: GetUSBCamera max concurrent tasks: 1 scheduling strategy: TIMER_DRIVEN scheduling period: 30 sec

Re: [NIFI-CPP] Issues with TIMER_DRIVEN and CRON_DRIVEN

El domingo, 22 de abril de 2018 23:00:24 (CEST) Marc P. escribió: > Is there an error or session rollback in the log file? Yes, I always get this error: [org::apache::nifi::minifi::io::Socket] [error] Could not bind to socket, reason Address family not supported by protocol But "everything"

Re: [NIFI-CPP] Issues with TIMER_DRIVEN and CRON_DRIVEN

That error is a connection attempt that may be the result of the flow. Feel free to create a ticket with the log file . A session roll back would indicate the problem you are seeing. I've been running getusbcamera and haven't run into the issue you suggest on an rpi but perhaps you have come