[
https://issues.apache.org/jira/browse/FALCON-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14224313#comment-14224313
]
Syed Zulfiqar Ali commented on FALCON-501:
------------------------------------------
High Level Solution:
1. Support EL, as well as date instance, as a value of 'start' and 'end' field
in 'validity'.
3. Make 'end' date an optional field. If not specified, Falcon will default it
to latest possible date.
3. NO support for 'never()'.
Implementation Details:
1. Relax validation of 'start' and 'end' field in 'validity' by changing the
type from 'date-time-type' to 'xs:string' in 'process-1.0.xsd'.
2. Enhance 'ProcessEntityParser.java' class. API will first try to create Date
object assuming it is a date instance. If it fails (exception is thrown) API
will try to create Date object assuming it is an EL expression. And perform
necessary validation.
3. Enhance 'OozieWorkflowEngine.java' class to transform EL expression to an
actual date instance while creating Oozie coordinator.
> EL expressions allowed inside of validity
> -----------------------------------------
>
> Key: FALCON-501
> URL: https://issues.apache.org/jira/browse/FALCON-501
> Project: Falcon
> Issue Type: Wish
> Reporter: Josh Clum
> Assignee: Syed Zulfiqar Ali
>
> I have a configuration that looks something like this:
> <clusters>
> <cluster name="cluster" type="source">
> <validity start="2014-06-09T13:00Z" end="2016-01-01T00:00Z"/>
> </cluster>
> </clusters>
> I would like to have a way to start the job on the day I submitted the job.
> Right now, processes seem to be playing "catchup" if I don't manually change
> the start date to the day I submit.
> It's complicated to have dates changing is such a way. It would be nice to
> have EL expressions like this:
> <clusters>
> <cluster name="cluster" type="source">
> <validity start="today(0,0)" end="never()"/>
> </cluster>
> </clusters>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
