[
https://issues.apache.org/jira/browse/FALCON-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14226264#comment-14226264
]
Srikanth Sundarrajan commented on FALCON-501:
---------------------------------------------
One of the sticky things I feel about this feature is to figure what happens
during entity update. There might be a bit of complexity in handling updates
correctly. [~zulfiali], Can you outline how the update would work with an
expression based start time.
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.
> 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)
