You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by Josh Clum <jo...@gmail.com> on 2014/07/08 15:16:42 UTC
Feed/Process Validity
Hi,
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. Is there any way to avoid this?
I have my jobs rolled up in rpms, and its 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>
Thoughts?
Thanks,
Josh
Re: Feed/Process Validity
Posted by Josh Clum <jo...@gmail.com>.
https://issues.apache.org/jira/browse/FALCON-501
On Wed, Jul 9, 2014 at 1:33 AM, Shwetha GS <sh...@inmobi.com> wrote:
> Josh,
>
> Can you please file a jira so that we can track this?
>
> Thanks,
> Shwetha
>
>
> On Tue, Jul 8, 2014 at 6:46 PM, Josh Clum <jo...@gmail.com> wrote:
>
> > Hi,
> >
> > 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. Is there any way to avoid
> this?
> >
> > I have my jobs rolled up in rpms, and its 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>
> >
> > Thoughts?
> >
> > Thanks,
> > Josh
> >
>
> --
> _____________________________________________________________
> The information contained in this communication is intended solely for the
> use of the individual or entity to whom it is addressed and others
> authorized to receive it. It may contain confidential or legally privileged
> information. If you are not the intended recipient you are hereby notified
> that any disclosure, copying, distribution or taking any action in reliance
> on the contents of this information is strictly prohibited and may be
> unlawful. If you have received this communication in error, please notify
> us immediately by responding to this email and then delete it from your
> system. The firm is neither liable for the proper and complete transmission
> of the information contained in this communication nor for any delay in its
> receipt.
>
Re: Feed/Process Validity
Posted by Shwetha GS <sh...@inmobi.com>.
Josh,
Can you please file a jira so that we can track this?
Thanks,
Shwetha
On Tue, Jul 8, 2014 at 6:46 PM, Josh Clum <jo...@gmail.com> wrote:
> Hi,
>
> 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. Is there any way to avoid this?
>
> I have my jobs rolled up in rpms, and its 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>
>
> Thoughts?
>
> Thanks,
> Josh
>
--
_____________________________________________________________
The information contained in this communication is intended solely for the
use of the individual or entity to whom it is addressed and others
authorized to receive it. It may contain confidential or legally privileged
information. If you are not the intended recipient you are hereby notified
that any disclosure, copying, distribution or taking any action in reliance
on the contents of this information is strictly prohibited and may be
unlawful. If you have received this communication in error, please notify
us immediately by responding to this email and then delete it from your
system. The firm is neither liable for the proper and complete transmission
of the information contained in this communication nor for any delay in its
receipt.
Re: Feed/Process Validity
Posted by Srikanth Sundarrajan <sr...@hotmail.com>.
+1 certainly useful
Sent from my iPhone
> On 08-Jul-2014, at 6:47 pm, "Josh Clum" <jo...@gmail.com> wrote:
>
> Hi,
>
> 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. Is there any way to avoid this?
>
> I have my jobs rolled up in rpms, and its 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>
>
> Thoughts?
>
> Thanks,
> Josh