Thanks, it helped.
On Wed, Apr 15, 2015 at 6:16 PM, Oussama Chougna <[email protected]>
wrote:
> Why would you parametrize the frequency time-unit? You'll bring yourself
> in more trouble since the datasets uri-templates depend on the frequency
> used. A coordinator is not supposed to run on different frequency intervals.
> Your solution is not working because the EL expression in the frequency
> attribute should resolve to a number, in your case it resolves to another
> EL expression which is not evaluated any further.
>
> One way you can parametrize the frequency is as follows:
> coordinator.propertiescoordinatorFrequencyInHours=2
> coordinator.xml:"${coord:hours(coord:conf('coordinatorFrequencyInHours'))}"
>
> Note that there is no way parametrizing the time-unit.
> Cheers,
>
>
>
>
> > Date: Wed, 15 Apr 2015 15:17:41 +0530
> > Subject: Urgent help please - coordinator properties file
> > From: [email protected]
> > To: [email protected]
> >
> > Hello,
> >
> > Can somebody quicky help me on the below scenario.
> >
> > Coordinator.properties file
> > freq=5
> > coordinator.xml
> > frequency="${freq}"
> > Now the above syntax taking file it is taking to run the job every 5
> > minutes.
> >
> > But the below thing is not happening for me.
> >
> > Coordinator.properties file
> > freq=coord:minutes(5)
> > coordinator.xml
> > frequency="${freq}"
> >
> > Error: Invalid coordinator application attributes, parameter
> [frequency] =
> > [coord:minutes(5)] must have 5 bit fields. Parsing error For input
> string:
> > "coord:minutes(5)"
> >
> > Actually, the business logic is to pass the data from properties file and
> > it should be in days/months/minutes and I am planning to use
> > coord:days(),coord:month()
> > etc
> > But it's not taking, the bottom line is our coordinator.xml/workflow.xml
> > will not change it will run the same job but in diffrent ways by days,
> > month and year.
> >
> > Please help
>
>
