[
https://issues.apache.org/jira/browse/FALCON-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Clum updated FALCON-501:
-----------------------------
Description:
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>
Summary: EL expressions allowed inside of validity (was: EL
expressions Allowed inside of )
> 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
>
> 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.2#6252)
