Keith,

Thanks. I wasn't at my phone before, so I didn't include any links but now that 
I'm sitting at a computer,
I was able to lookup the JIRA for this [1] and the PR for this [2].

If you want to, you can go to the JIRA and 'Watch' it so that you're notified 
when there are any comments
or updates to the JIRA so that you can track its progress. Also, if you are the 
type who likes to try out patches,
feel free to build it yourself and provide any feedback that you have!

Thanks
-Mark

[1] https://issues.apache.org/jira/browse/NIFI-401 
<https://issues.apache.org/jira/browse/NIFI-401>
[2] https://github.com/apache/nifi/pull/512 
<https://github.com/apache/nifi/pull/512>


> On Jun 16, 2016, at 6:25 PM, Keith Lim <[email protected]> wrote:
> 
> Thanks Mark.  I appreciate the effort and the quality work that you guys are 
> doing.  
> 
> Thanks,
> keith
> From: Mark Payne <[email protected] <mailto:[email protected]>>
> Sent: Thursday, June 16, 2016 3:13 PM
> To: [email protected] <mailto:[email protected]>
> Subject: Re: Scheduling using CRON driven on Windows OS
>  
> Keith,
> 
> I believe there already is a PR for this. I did an initial review and things 
> looked good but it touches some very critical parts of the application and 
> needs to be scrutinized and reviewed much more thoroughly before being merged 
> in. 
> 
> Thanks
> -Mark
> 
> Sent from my iPhone
> 
> On Jun 16, 2016, at 5:39 PM, Keith Lim <[email protected] 
> <mailto:[email protected]>> wrote:
> 
>> Just found out from my coworker the NiFi is running on a cluster of 20 
>> nodes, hence the 20 flowfiles generated.  
>> 
>> Also found out that when the NiFi is hosted in the clustered environment, 
>> there is an additional option for Scheduling Strategy: On Primary Node
>> This options ensures that the processor only runs on the primary node 
>> (single node) using the run schedule time defined. 
>> So, as it is I can do Cron but have to be subjected to the number of nodes 
>> in the cluster or using the On Primary Node option to run on single node but 
>> do not have CRON option. 
>> 
>> I wish the On Primary Node option can be applied to both Time Driven and 
>> Cron Driven, i.e. a separate checkbox.    
>> 
>> Is there any workaround for this?   If not could we prioritize this as an 
>> enhancement?
>> 
>> Thanks,
>> Keith
>> From: Bryan Bende <[email protected] <mailto:[email protected]>>
>> Sent: Thursday, June 16, 2016 1:45 PM
>> To: [email protected] <mailto:[email protected]>
>> Subject: Re: Scheduling using CRON driven on Windows OS
>>  
>> Does 0 0/2 * * * ?  work?
>> 
>> Another option, if you don't care about it being on the exact time 
>> boundaries, you could use the timer driven scheduling and set it to 120 
>> seconds, that would be every 2 minutes from when the processor starts.
>> 
>> On Thu, Jun 16, 2016 at 4:23 PM, Keith Lim <[email protected] 
>> <mailto:[email protected]>> wrote:
>> I have a follow up question.
>> 
>> I want 1 flowfile generated every two minutes: 00 */2 * * * ?   ( I have 
>> tried * */2 * * * ?,  0 */2 * * * ?  00 00/02 * * * ? and  as well)
>> but instead I am seeing 20 flowfiles generated every two minutes.
>> I even set the Yield Duration to 5 secs just to see if it does any thing, 
>> but I am not able to get it to generate only 1 flowfile every two minutes. 
>> 
>> Thanks,
>> Keith
>> 
>> From: Keith Lim <[email protected] <mailto:[email protected]>>
>> Sent: Thursday, June 16, 2016 10:44 AM
>> 
>> To: [email protected] <mailto:[email protected]>
>> Subject: Re: Scheduling using CRON driven on Windows OS
>>  
>> Thanks for pointing this out.  My bad for not referring to the NiFi 
>> documentation.   When I saw the Cron Driven and presented with the default 
>> "* * * * * ?", my instinct was to reference a standard Linux/Unix Cron 
>> format.
>> 
>> Thanks,
>> Keith
>> From: Bryan Bende <[email protected] <mailto:[email protected]>>
>> Sent: Thursday, June 16, 2016 10:19 AM
>> To: [email protected] <mailto:[email protected]>
>> Subject: Re: Scheduling using CRON driven on Windows OS
>>  
>> Also, the user guide has a description of the scheduling strategies which 
>> described the cron format:
>> 
>> https://nifi.apache.org/docs/nifi-docs/html/user-guide.html#scheduling-tab 
>> <https://nifi.apache.org/docs/nifi-docs/html/user-guide.html#scheduling-tab>
>> 
>> On Thu, Jun 16, 2016 at 1:17 PM, Pierre Villard <[email protected] 
>> <mailto:[email protected]>> wrote:
>> Hi Keith,
>> 
>> This is the expected behavior, the first parameter is indeed seconds so that 
>> */5 * * * * ? will generate a FF every 5 seconds.
>> In your case, I believe you'd like something like 00 02 10 * * ?
>> 
>> Hope this helps.
>> 
>> 2016-06-16 19:13 GMT+02:00 Keith Lim <[email protected] 
>> <mailto:[email protected]>>:
>> My GenerateFlowFile processor is enabled and started
>> with  
>> 
>> Scheduling Strategy: Cron Driven
>> Run Schedule : 02 10 * * * ?
>> 
>> This I expects to generate a flow file daily at 10:02 am, but from my 
>> limited test, it seems to take the second parameter as minutes, and generate 
>> a flowfile hourly at 10 minutes after the hour, e.g. 10:10, 11:10, 12:10, 
>> 13:10...
>> Perhaps there is a bug in parsing system date format? 
>> 
>> Attached is a simple template that I am using for testing.   
>> 
>> Thanks,
>> Keith
>> 
>> From: Andrew Grande <[email protected] <mailto:[email protected]>>
>> Sent: Wednesday, June 15, 2016 4:10 PM
>> To: [email protected] <mailto:[email protected]>
>> Subject: Re: Scheduling using CRON driven on Windows OS
>>  
>> Keith,
>> Was your processor running at all times? It has to be started and enabled.
>> I guess sharing the cron expression and maybe a quick screenshot will help 
>> next.
>> Andrew
>> 
>> On Wed, Jun 15, 2016, 6:58 PM Keith Lim <[email protected] 
>> <mailto:[email protected]>> wrote:
>> I tried setting Scheduling Strategy property to CRON Driven but does not 
>> seem to work.   Sometimes it would fire when not expected to and others not 
>> fire when expected to. 
>> This is on Windows OS and the processor I tried was GenerateFlowFile.  Is 
>> CRON Driven setting not designed to work on Windows OS?
>> 
>> Thanks,
>> Keith

Reply via email to