falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ajay Yadav (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-501) EL expressions allowed inside of validity
Date Thu, 27 Nov 2014 05:13:13 GMT

    [ https://issues.apache.org/jira/browse/FALCON-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14227267#comment-14227267

Ajay Yadav commented on FALCON-501:


Also one another issue is our mis-use of start-time to figure the execution schedule. With
an expression for start time, it is quite hard to determine and control the schedule. This
is an orthogonal issue though perhaps need to be addressed in an independent jira.
There is already a JIRA for it - FALCON-664

> 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

View raw message